You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Enroot does not expose anything and does not use Dockerfiles at all.
Whatever your programs listen to in the container, they listen to outside of the container.
There is no treatment of network ports.
@jolyons123 Were you able to get interactive debugging with vscode working on slurm gpu jobs? I've tried adapting the gist you linked to our cluster (LRZ AI Systems in Germany), but it fails so far.
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.
The text was updated successfully, but these errors were encountered: