Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support network option #191

Open
obonyojimmy opened this issue Nov 23, 2022 · 1 comment
Open

support network option #191

obonyojimmy opened this issue Nov 23, 2022 · 1 comment

Comments

@obonyojimmy
Copy link

i propose a new field , networks that can be used to attach network/s to the running container ie docker run -itd --network=my-net busybox

@uniqueg
Copy link
Contributor

uniqueg commented Nov 28, 2022

Thanks a lot for the suggestion @obonyojimmy. Would you mind elaborating a bit on the use case(s) you would like to address with this? I think that this is an interesting idea that might be able to address service dependencies that an individual job may have (a use case/limitation that we have been just recently facing). However, I would like to know what you have been thinking.

Also, possible concern may be that networks are not necessarily supported by solutions that are not based on Docker (not sure about Singularity, but certainly I don't see how, for example, how Conda would be able to support this). But that might be addressed by making this an optional feature/capability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants