-
Notifications
You must be signed in to change notification settings - Fork 29
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
Nvidia-docker2 #23
Comments
My problem was solved! |
Hi @cyberwillis, if you figured out a good way to integrate it, would you mind sharing? I'm curious how you resolved this question. |
Hi again... So investigating a little here, I found that the specific runtime can be set in /etc/docker/daemon.json { "default-runtime": "nvidia", "runtimes": { "nvidia": { "path": "/usr/bin/nvidia-container-runtime", "runtimeArgs": [ ] } } } by using this the docker-compose started to work again, because eliminates the necessity of pass this argument all the time. Probably nvidia-docker-compose will also work now ... I don't get a time to test. I do have a big chain of images to build and run to be sure about this solution. Also to complement nvidia-docker-plugin does not exist anymore. [UPDATE] : fixed the syntax of daemon.json |
Yes I confirm, my problem is solved and I get back on track and docker-compose alone is doing everything now. I am not using nvidia-docker-compose because probably it's trying to do something else involving nvidia-docker-plugin that is not needed anymore. |
@cyberwillis thanks a lot for sharing this! |
It looks like docker-compose will be gaining a "runtime" option for the 2.3 schema next release, which will enable an alternative to setting default-runtime in daemon.json. See docker/compose#5405. |
That works well for me. Thanks. |
any way to use it with nvidia-docker2 alpha ?
The text was updated successfully, but these errors were encountered: