This message was deleted.
# k3s
a
This message was deleted.
c
There is no standalone containerd service when you’re using k3s. There is only k3s, with containerd, kubelet, and everything else embedded in it.
what were you seeing that made you expect us to install a standalone containerd service on your node?
n
Hey Brandon, thank you for the reply! I was actually following a guide where they used containerd on kind.
I assume the same would be
systemctl restart k3s
right?
c
yep
kind and k3s are not really at all the same, unless you are running k3s in docker. Or is k3s actually installed on your node?
n
No, I am running k3s with containerd, the kind node internally uses containerd.
c
if you’re running k3s as a docker image, you might look at k3d
👀 1
well your node doesn’t have containerd installed, so I’m assuming that you’re just using the containerd that is built into k3s
n
Bingo!
c
you can use it with standalone containerd, which is why I asked what you were expecting
👍 1
n
It's actually quite convenient in this way with k3s.
Thanks for the info!
👍 1