Skip to content
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

container toolkit daemon only cleans up containerd runtime config, and doesn't clean up the nvidia container runtime binaries on host /user/local/nvidia #494

Open
wyike opened this issue May 13, 2024 · 0 comments

Comments

@wyike
Copy link

wyike commented May 13, 2024

I also see code here https://gitlab.com/nvidia/container-toolkit/container-toolkit/-/blob/main/tools/container/nvidia-toolkit/run.go?ref_type=heads#L131-140. It only reset the container runtime config.

After gpu operator or container toolkit removal, the nvidia/toolkit will be left on host:

worker/d3067738-6590-433d-8dd5-2568f7bccbb9:~# ls /usr/local/nvidia/toolkit/
libnvidia-container-go.so.1       nvidia-container-cli          nvidia-container-runtime.cdi.real   nvidia-container-runtime.legacy.real  nvidia-ctk.real
libnvidia-container-go.so.1.15.0  nvidia-container-cli.real     nvidia-container-runtime-hook       nvidia-container-runtime.real
libnvidia-container.so.1          nvidia-container-runtime      nvidia-container-runtime-hook.real  nvidia-container-toolkit
libnvidia-container.so.1.15.0     nvidia-container-runtime.cdi  nvidia-container-runtime.legacy     nvidia-ctk

Asking here if it is an intentional design or some cleanup step we have missed. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant