Nvidia support?
See original GitHub issueI know that a PR was being worked on to provide nvidia support, but apparently it is no longer necessary with nvidia-docker2
, but I cannot find anything in the documentation.
Is it currently possible (provided nvidia-docker2
is properly installed/configured) to do the equivalent of:
It looks like this is available via the runtime
parameter?
docker run --runtime=nvidia nvidia/cuda nvidia-smi
and as of v17.12.0-ce
:
docker service create -t --generic-resource "gpu=1" nvidia/cuda nvidia-smi
It looks like the resources
API does not support --generic-resource
…
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Access Customer Support - NVIDIA
NVIDIA's customer support services are designed to meet the needs of both the consumer and enterprise customers.
Read more >GeForce Product & Technical Support - NVIDIA
Find answers to the most common questions and issues. Our knowledgebase is ...
Read more >Customer Support, Knowledgebase, and FAQs - NVIDIA
Get help with your online order, browse trending support topics, visit and ...
Read more >Official Drivers - NVIDIA
Download latest drivers for NVIDIA products including GeForce, TITAN, NVIDIA RTX, Data Center, GRID and more. ... Need help? Technical Support ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah I am interested in implementing this. I’ll open a PR soon.
So I see a few options for implementing this:
1. Most explicit:
pros:
value='1'
on the userdocker.types.NamedGenericResource(kind='GPU', value=1)
cons:
2. Determine
NamedResourceSpec
andDiscreteResourceSpec
automatically with anisinstance()
check:pros:
cons:
3. Use a list of
dict
and determineNamedResourceSpec
andDiscreteResourceSpec
automatically with anisinstance()
check:pros:
cons:
isinstance()
and allstr
values will be aNamedResourceSpec
and allint
values will beDiscreteResourceSpec
.4. Use a list of
str
and determineNamedResourceSpec
andDiscreteResourceSpec
automatically with anisinstance()
check:pros:
cons:
And for all cases, use
generic_reservations
like:What are your thoughts? Or does it not matter? There seems to be some variation of each throughout the existing API…
I have them all pretty much coded up so it doesn’t a lot to me but I am partial to either 1 or 3