Open jolyons123 opened 1 month ago
Enroot does not expose anything and does not use Dockerfile
s at all.
Whatever your programs listen to in the container, they listen to outside of the container.
There is no treatment of network ports.
Thank you!
According to this gist, enroot automatically exposes the port specified with the EXPOSE statement in the docker file to the same port on localhost. Is there a way to customize this? What if multiple containers try to expose the same port?
Our use-case is that we want to have interactive debugging capabilities (ssh connection for vscode/pycharm or expose a jupyter server) for our slurm gpu jobs.