-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
crictl info does not match containerd.toml #11631
Comments
Please read the docs: https://docs.k3s.io/advanced#configuring-containerd K3s does not use |
Thank you @brandond ! Once I create the And last question: should I see the changes reflected when running |
Just restart the service. And yes. |
@brandond Sorry to bother you again but I'm not practical with Go templates, how should my
Do I just copy and paste this configuration and edit the line? |
Why are you trying to change that bit? That should be set to true if k3s is running under systemd. If k3s is not running under systemd it will automatically be set to false. |
Because I am using NVIDIA MPS in the cluster, this means I am not using the GPU Operator but the standalone nvidia-device-plugin which has this known issue. One of the workarounds is to set SystemCgroup to false in the nvidia runtime options. |
Using this
|
Copy everything from here: https://github.com/k3s-io/k3s/blob/v1.32.0%2Bk3s1/pkg/agent/templates/templates_linux.go#L12-L105 Change line https://github.com/k3s-io/k3s/blob/v1.32.0%2Bk3s1/pkg/agent/templates/templates_linux.go#L104` from |
I am experiencing an issue with the NVIDIA device plugin on my k3s cluster after enabling MPS mode. In fact switching from the GPU-Operator to the standalone nvidia-device-plugin, every time a
systemctl daemon-reload
is triggered, my pods lose access to the GPUS (NVIDIA/nvidia-container-toolkit#48).As the official issue suggest, a workaround should be changing the
/etc/containerd/config.toml
in order to setSystemdCgroup = false
.Even if I do this, when I run
crictl info
this is the configuration I have for the nvidia runtime:While this is my containerd configuration:
How can I change the configuration I get when running
crictl info
to change theSystemdCgroup
?The text was updated successfully, but these errors were encountered: