-
Notifications
You must be signed in to change notification settings - Fork 160
Non-default nvidia-container-runtime-hook config file #47
Comments
Aside from this issue, I also suggest adding |
Thanks @AkihiroSuda I encountered this issue exactly because I'm running rootless docker with nvidia runtime using your usernetes. Everything works, except have to set |
Coincidence 👍 |
Hello! This feature is already present, you can set the config flag to point to a different file:
|
@RenaudWasTaken How the Could you reopen the issue? |
@RenaudWasTaken I don't run |
An easy way for you to set it is to create a shell wrapper:
|
Thanks @RenaudWasTaken got it working by adding this file to #!/bin/sh
/usr/bin/nvidia-container-runtime-hook -config=... "$@" |
This breaks DEB/RPM |
@AkihiroSuda I got it working by leaving #!/bin/sh
/usr/bin/nvidia-container-runtime-hook -config=... "$@" But I agree it would be nicer if |
Ack, I'll keep this issue open |
PR: #50 |
This enhancement is addressed in f6b61c4 |
Not yet :D! |
I think this change is only for the runtime and not for the hook no? |
@Ethyling Ah yes you are correct |
I am closing this issue. I know that we may not have completly added the requested feature, but given the changes in the architecture since this was opened, I would propose that a new issue is created with updated requirements if a need still exists. |
Hi I'm not sure if this is correct but it looks like the path to
config.toml
fornvidia-container-runtime-hook
is hard-coded herenvidia-container-runtime/hook/nvidia-container-runtime-hook/hook_config.go
Line 12 in 03af0a8
which means if I want to use a config file located somewhere else I need to edit the code and recompile?
Is it a good idea to make this path configurable via an arg to
nvidia-container-runtime
or an environment variable? I can submit a PR if that's the case.The text was updated successfully, but these errors were encountered: