[Feature]: Regenerate CDI specs on MIG device changes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, go
- Domain
- devops, infrastructure
Research direction
Start with nvidia-cdi-refresh.service and the existing response to driver changes. Trace how MIG device reconfiguration is detected and how CDI specs are generated; done means valid specs are regenerated after MIG changes and work with native CDI support in Docker or Podman.
Written by the indexing model from the issue text.
Description
The nvidia-cdi-refresh.service responds to driver changes, but does not respond to MIG device reconfiguration. This means that there are no valid CDI specs for MIG devices when using native CDI support in Docker or Podman, for example.
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 609
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 37
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from NVIDIA/nvidia-container-toolkit
-
[Bug]: Containers with NVIDIA_VISIBLE_DEVICES=all fail to start in jit-cdi mode when every GPU is bound to vfio-pciPossibly taken @efegokdemir claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
NVIDIA/nvidia-container-toolkit#2163 ·
Maintainers usually reply within 1 day
-
Address TODO comments in internal/platform-support/dgpu/dgpu.goPossibly taken @truongbo17 claimed this 33 days ago. Opendsx-ws-0930 good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NVIDIA/nvidia-container-toolkit#2114 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
NVIDIA/nvidia-container-toolkit#2197 ·
Maintainers usually reply within 1 day
-
[Bug]: Containerized installer removes the existing Toolkit installation before the replacement is complete and durablePossibly taken @henry118 claimed this 13 days ago. Openbug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NVIDIA/nvidia-container-toolkit#2153 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
NVIDIA/nvidia-container-toolkit#2147 · 1 comment ·
Maintainers usually reply within 1 day
All issues in NVIDIA/nvidia-container-toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
component/tests needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NVIDIA/nodewright#967 ·
Maintainers usually reply within 1 day
-
apm:ecosystem needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
DataDog/dd-trace-go#5815 ·
Maintainers usually reply within 2 days
-
Build releases with Go 1.26.10+ for CVE-2026-111943 (eMudhra intermediate CA compromise)Possibly taken @zoezhangmattr claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
auth0/terraform-provider-auth0#1778 ·
Maintainers usually reply within 2 days
-
area:sampler tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jmbarzee/temporal-architect#302 ·
Maintainers usually reply within 1 day