[Feature Request] Ship DCGM packages in the NVIDIA driver local repository installer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reviewing how the nvidia-driver-local-repo--.(deb|rpm) installers are published under the NVIDIA driver local_installers path, and how companion packages such as nvidia-fabricmanager are included. Done means DCGM packages are shipped in the driver local repository with each release and their driver/DCGM compatibility is validated by construction.
Written by the indexing model from the issue text.
Description
Summary
Please consider including the DCGM packages in the NVIDIA driver local repository installers
(nvidia-driver-local-repo-<distro>-<version>.(deb|rpm) published under
https://developer.download.nvidia.com/compute/nvidia-driver/<version>/local_installers/).
Motivation
Including DCGM alongside the driver in the local repo would let consumers install everything from one source, with cross-compatibility guaranteed by construction.
The driver local repo is already the single, self-contained artifact we use to install the driver and companion packages such as nvidia-fabricmanager.
Having DCGM distributed separately has two costs for us:
- Supply chain complexity. Every additional source means separate artifacts to mirror, verify, pin, and track through their lifecycle.
- Compatibility burden. today we must check the cross compatibility between driver/CUDA/DCGM, which comes with risks of taking the wrong decision. If DCGM shipped inside the driver local repo, each driver release would carry a DCGM version validated against it, making the pairing correct by construction.
Thanks for considering it.
- Dominant language
- C++
- Stars
- 800
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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/DCGM
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
dcgmi InstallCtrlHandler unhandled returnMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
After a failed `lshw` parse in `SysMon`, the CPU hierarchy call never returns, so `dcgm-exporter` never binds its portPossibly taken @xibolun claimed this 2 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#4011 ·
-
docs(simulation): Quickstart publishes UDP 14550, which the SITL images' own docs say not to doOpenstatus:needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
PX4/PX4-Autopilot#29292 · 1 comment ·
Maintainers usually reply within 1 day
-
I/O internal correctness medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Mac mini M6 (16 GB): Q2_0 streaming works - measured 11.7->27.2 tok/s + arena fix for sub-32 GB MacsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day