-
Couldn't load subscription status.
- Fork 427
Use GO API for toolkit installation #704
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
Conversation
31ca649 to
43f3ad5
Compare
|
I was able to validate these changes in gpu-operator after setting the I've filed a PR in gpu-operator to consume this change: NVIDIA/gpu-operator#1019 |
|
|
||
| options := options{} | ||
| options := options{ | ||
| toolkitOptions: toolkit.Options{}, |
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.
Do we also need this?
| toolkitOptions: toolkit.Options{}, | |
| toolkitOptions: toolkit.Options{}, | |
| runtimeOptions: runtime.Options{}, |
This change converts the toolkit installation logic to a go package and invokes this installation over the go API instead of starting this executable. Signed-off-by: Evan Lezar <[email protected]>
Signed-off-by: Evan Lezar <[email protected]>
Signed-off-by: Evan Lezar <[email protected]>
Signed-off-by: Evan Lezar <[email protected]>
Signed-off-by: Evan Lezar <[email protected]>
43f3ad5 to
fd708cd
Compare
|
Opened a rebased version of this from my fork #722 |
|
Closing as this is superseded by #722 |
This change switches from invoking the
toolkit installcommand when installing the NVIDIA Container Toolkit from the toolkit container to invoking the GO API directly.This is also done for the
{{ .Runtime }} setupand{{ .Runtime }} cleanupcommands.This allows for a clearer dependence between the runtime installation and configuration and the toolkit installation.
Note that this assumes that the generic envvars are used instead of
DOCKER_,CONTAINERD_,CRIO_envvars where applicable and also drops support for theRUNTIME_ARGSenvvar. This should be validated with the GPU Operator versions that we expect to consume this.