NVIDIA / NVIDIA/nvidia-container-toolkit
Suggestion: Self-diagnostic command
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 592
- Avg merge
- 1d 33m
- Merged PRs (30d)
- 61
Description
My experience with the NVIDIA Docker integration across two PCs and a few Jetson devices is that it can be a bumpy experience, and the error messages are often fairly inscrutable. I've had a working system break a few days later due to an unattended upgrade.
It would probably help reduce the number of support requests if there were a self-diagnostic script that could look for common misconfiguration issues and/or format a bug report with all the relevant info for the user. The Homebrew project does this (brew doctor) and it turns out to be convenient for both users and project admins.
Over 1,500 issues have been filed to this repo and 1 in 5 mention some "Error response from daemon" message, like this one that doesn't give me enough information to remedy the situation.
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: nvml error: insufficient permissions: unknown.
This problem appears to be related to permissions of /dev/nvidia* when virtualgl is set up on the host. Solution comment. This is an example of something that would be really easy for a script to detect but takes a bit of digging for the user to solve. (Also it hopefully wouldn't be that hard to say something more useful than "unknown" in this error message.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the NVIDIA Docker integration and the example failure involving /dev/nvidia* permissions with virtualgl. Done should include a self-diagnostic command that detects common misconfigurations and can format relevant information for users and project administrators.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100