-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nvidia-container-toolkit: 1.15.0-rc.3 -> 1.17.3 #367769
base: master
Are you sure you want to change the base?
Conversation
74df01b
to
fd6df1a
Compare
fd6df1a
to
e4bdd22
Compare
e4bdd22
to
31395de
Compare
9116aaf
to
30db459
Compare
30db459
to
70da757
Compare
@@ -37,9 +37,9 @@ writeScriptBin "nvidia-cdi-generator" '' | |||
${lib.getExe' nvidia-container-toolkit "nvidia-ctk"} cdi generate \ | |||
--format json \ | |||
--device-name-strategy ${deviceNameStrategy} \ | |||
--ldconfig-path ${lib.getExe' glibc "ldconfig"} \ | |||
--ldconfig-path ${lib.getExe' glibc.bin "ldconfig"} \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, I thought getExe
would select .bin
automatically?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, will update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, thank you keeping up the work on nvidia ctk! Anything missing for this PR to be undrafted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! I am checking some behaviors with the hooks and in particular with #366109.
When I'm done with the checks I'll move it out of draft. In FHS distros (e.g. ubuntu) I see that hooks are not working as expected and I want to understand what is going on exactly. Similar with NixOS containers, although different, given we don't have ldcache we'd need to fallback to LD_LIBRARY_PATH, but I don't see a good strategy there, given OCI hooks don't allow us to "augment" the envvar (e.g. LD_LIBRARY_PATH=something/new:$LD_LIBRARY_PATH).
I could just bump the version and continue these checks in parallel but let me do a quick check and if I see it's taking longer than expected we can just bump and investigate afterwards.
Fixes: #341911
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.