-
Notifications
You must be signed in to change notification settings - Fork 2k
Support for containerd due to Kubernetes 1.20 changes on ARM64 devices #1468
Comments
It looks like your Also you add fields that match those higher up in your template, e.g.:
Not sure how that is treated either. |
Thank you for making this clear. I have tested
And it seems to work with
Thank you |
Great to hear. Please close this issue if you consider it resolve now. |
Hey @klueska, any chance you could take a look at k3s-io/k3s#3054 (comment)? Basically, I had a mistake in my previous comment and nvidia runtime didn't work properly (it didn't mount cuda and other libs). After fixing it following https://k3d.io/v4.4.8/usage/guides/cuda/, I was curious where I could learn why this solution works and how things actually work behind scene in regards to containerd's configuration file. Thank you |
1. Issue or feature description
Kubernetes is deprecating docker support starting 1.20. As a result of this change we would have to adjust our kubernetes clusters to use containerd as our CRI.
As part of our stack, we use nvidia-docker to make use of our Jetson Xavier GPUs together with k3s and docker as CRI.
I have followed @klueska's comment at containerd/containerd#4834 (comment) and ended up with the following information:
Once set, I have ran
sudo service k3s restart
and then:When using docker with
runtime=nvidia
:How could I make this work on my Jetson Xavier?
Thank you
Shaked
The text was updated successfully, but these errors were encountered: