It looks like if I run sudo docker-compose start after boot, the remaining containers that didn't auto-start will spin up. I am not seeing anything in the docker-compose.yml file that stands out that wouldn't start specific containers.
Hello,
Please double check this: sudo chown -R 1001:1001 data/mongo-data
Did you change the mongo db permissions before running docker compose ?
We also got report that some zip install were getting corrupted while downloaded via Chrome.
Try to download install file from Firefox instead.
By the way, Cloud Exchange 3.3 in now GA. You may want to give it a try.
The permissions are correct on the mongo repository. These permissions were not changed, as I followed the instructions on github, with cloning the repo via git (not downloading with a browser), and running ./setup & ./start, which run provided scripts by Netskope. The only reason I ran docker-compose was due to the issue with RabbitMQ starting after reboot.
Working with someone at Netskope last week, they verified this is an issue and he put a ticket in to get this resolved. Also moving to 3.3 doesn't resolve the issue.
docker is set to start at boot?
sudo systemctl enable docker
@ryans this was a known issue with the .yaml file settings, and has been resolved in 3.3.1 release. https://github.com/netskopeoss/ta_cloud_exchange/commit/72ba556d42d5ab35c485de0402a2d46129133c64
Confirmed issue is resolved after reboot of Docker host.
Hi, Im having the same issue. Just installed All the required docker components, git and python, but when starting Netskope using ./start, the UI displays Bad Gateway error. I followed the instruction from here and from https://community.netskope.com/t5/Additional-Discussions/Cloud-Exchange-not-staying-up-Bad-Gateway/m-p/2139
but everytime after running ./setup, I checked the ta_cloud_exchange dir all permissions resets back to 999.
ANy ideas?
Thanks WS
