Skip to content

nvproxy: don't pass privileged driver caps to nvidia-container-cli#13377

Open
luiscape wants to merge 1 commit into
google:masterfrom
luiscape:luis/nvidia-driver-capability-bug
Open

nvproxy: don't pass privileged driver caps to nvidia-container-cli#13377
luiscape wants to merge 1 commit into
google:masterfrom
luiscape:luis/nvidia-driver-capability-bug

Conversation

@luiscape
Copy link
Copy Markdown
Contributor

@luiscape luiscape commented Jun 5, 2026

Setting NVIDIA_DRIVER_CAPABILITIES=all with any of the gvisor "privileged" driver capabilities, for example
--nvproxy-allowed-driver-capabilities=all,profiling crashed runsc on startup (exit status 2):

NVIDIAFlags() panicked on CapProfiling, which has no nvidia-container-cli flag

This changes how those flags are parsed by changing NVIDIAFlags() so that "privileged" capabilities (CapProfiling, CapFabricIMEXManagement) are skipped when parsing instead of panicking. I'm also adding a regression test.

Setting NVIDIA_DRIVER_CAPABILITIES=all with
--nvproxy-allowed-driver-capabilities=all,profiling crashed runsc on
startup (exit status 2): NVIDIAFlags() panicked on CapProfiling, which
has no nvidia-container-cli flag.

Privileged caps (CapProfiling, CapFabricIMEXManagement) are enforced
internally by nvproxy, so NVIDIAFlags() now skips them instead of
panicking. Adds a regression test.
@@ -0,0 +1,68 @@
// Copyright 2024 The gVisor Authors.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants