NVIDIA / enroot

A simple yet powerful tool to turn traditional container/OS images into unprivileged sandboxes.
Apache License 2.0
649 stars 94 forks source link

Is there a way to specify port bindings? #199

Open jolyons123 opened 4 months ago

jolyons123 commented 4 months ago

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.

krono commented 4 months ago

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 commented 4 months ago

Thank you!

tomasruizt commented 1 week ago

@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.

krono commented 1 week ago

Maybe a comment on the gist is more fruitful?