Use auto find runtime configfile inject in containerd config.toml then containerd startup failed about k3s

[brandond]

what exactly have you blurred out in your screenshot there? Is there some reason you can't include the actual log, instead of a redacted screenshot?

Can you confirm that you're not using a custom containerd.toml.tmpl?

According to your other oddly-redacted screenshot you are using v1.28.6+k3s1 which does not include the PR you linked. That change was added in v1.28.7+k3s1.

I am able to successfully use a detected alternative container runtime under both v1.28.6+k3s1 and v1.28.7+k3s1:

Mar 20 08:12:52 systemd-node-1 k3s[3002]: time="2024-03-20T08:12:52Z" level=debug msg="Searching for nvidia container runtime"
Mar 20 08:12:52 systemd-node-1 k3s[3002]: time="2024-03-20T08:12:52Z" level=info msg="Found nvidia container runtime at /usr/bin/nvidia-container-runtime"
Mar 20 08:12:52 systemd-node-1 k3s[3002]: time="2024-03-20T08:12:52Z" level=debug msg="Searching for nvidia-experimental container runtime"
Mar 20 08:12:52 systemd-node-1 k3s[3002]: time="2024-03-20T08:12:52Z" level=debug msg="Error searching for nvidia-experimental in $PATH: exec: \"nvidia-container-runtime-experimental\": executable file not found in $PATH"

systemd-node-1:/ # kubectl get node -o wide
NAME             STATUS   ROLES                  AGE     VERSION        INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION   CONTAINER-RUNTIME
systemd-node-1   Ready    control-plane,master   4m47s   v1.28.7+k3s1   172.17.0.7    <none>        openSUSE Leap 15.4   6.6.0-1001-aws   containerd://1.7.11-k3s2

systemd-node-1:/ # tail /var/lib/rancher/k3s/agent/etc/containerd/config.toml




[plugins."io.containerd.grpc.v1.cri".containerd.runtimes."nvidia"]
  runtime_type = "io.containerd.runc.v2"
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes."nvidia".options]
  BinaryName = "/usr/bin/nvidia-container-runtime"
  SystemdCgroup = true

[brandond]

Please provide specific steps to reproduce your issue. I suspect you're using a custom containerd config template, and your issue is unrelated to the runtime detection PR you linked. Without complete, unredacted logs its impossible to say.