-
Notifications
You must be signed in to change notification settings - Fork 309
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
added a config option for easy gpu sharing to DockerSpawner #473
Conversation
Thanks for submitting your first pull request! You are awesome! 🤗 |
for more information, see https://pre-commit.ci
This reverts commit 661ee8c.
Thanks for the PR and sorry for the delays! Trying to get this repo back on track. I think in general, we do not want to add new DockerSpawner-specific ways to express generic docker options that already work with the pass-through |
Hi. Sorry for the late response. I am having a bit of academic pressure on my back right now. One more thing is, at least at the time that I needed to add gpu, the device request part of the docker-py docs, was not complete and not helpful at all. Again, I understand your argument and believe it is valid. I am just trying to bring ideas that how this option would benefit some people. Thanks! |
Thanks for your input! What distinguishes cpu and memory limits is that they are standardized by jupyterhub, so all Spawners have the same configuration for implementing a consistent resource limit. There is not an equivalent for GPUs. If it is possible with the passthroughs we have, perhaps the right thing to add is an example showing how to do it with extra_host_config. |
Hmmm. Yes I think it is best to keep it as is but include an example. Thank you! |
I added a config option:
gpu_ids
to make sharing GPUs with containers a little bit easier and tried to keep the style close tocpu_limit
andmem_limit
.Also, How it works is documented with the help parameter.
Edit: I'm kind of new to the open-source community, sorry if something is missing. comments are appreciated!