fix(device-plugin): mount vgpu lock path in container to tmpfs in host#11
Merged
dkeven merged 1 commit intofeat/nvsharefrom Jan 14, 2026
Merged
fix(device-plugin): mount vgpu lock path in container to tmpfs in host#11dkeven merged 1 commit intofeat/nvsharefrom
dkeven merged 1 commit intofeat/nvsharefrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
The current vgpu lib lock mechanism, by creating/removing lock file in
/tmp/vgpuis prune to events such as machine reboot, leaving the lock uncleaned up, we change this to be mounted in the Linux tmpfs/runto make it cleaned up across machine reboots.