We're starting to ramp-up our use of running DevTest in containers instead of standalone installations. In doing so, we noticed that services hosted in the VSC are not properly exposed outside the host, and are thus serve no use.
Interestingly, the documentation for running the VSC is something similar to: sudo docker run -d --restart=always --name VSE -p 2013:2013 devtest/servers-base opt/devtest/bin/VirtualServiceEnvironment -n tcp://hostname:2013/VSE -m tcp://registry_host:2010/Registry
It appears that the only post exposed is VSC's own port 2013. Hosting services inside the VSC container will not be reachable outside the host. Has anyone worked-out a solution to this? We're considering adding the --net=host argument but not sure if this is the best way forward.