This message was deleted.
# rke2
a
This message was deleted.
c
never seen that before. containerd and kubelet are child processes of the main rke2 process and should be terminated when it exits. How exactly are you running rke2?
Also yeah you are a couple months out of date. Upgrade first, and see if this continues.
m
Copy code
sudo rke2 server --config <config_path> --cluster-reset --cluster-reset-restore-path <snapshot_path>
c
I have seen weird behavior when using sudo. Try getting a full root shell with su instead.
m
With version 1.34.4 I see 4 containerd-shim leftover processes, when running in a root shell (I have a modified data-dir, if that adds some relevant information).
Copy code
root      377417       1  0 17:03 pts/0    00:00:00 /xxxx/rke2/data/v1.34.4-rke2r1-0d52262ea640/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id b2f6493a8f97bdbc895b5e260140c5ed6c079eec2240ad8dbf5f213e58349316 -address /run/k3s/containerd/containerd.sock
root      377418       1  0 17:03 pts/0    00:00:00 /xxxx/rke2/data/v1.34.4-rke2r1-0d52262ea640/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id a6c35309234547fe1508074d4f46cfaf6b1df1782386f9713569cabf061e36c1 -address /run/k3s/containerd/containerd.sock
root      377419       1  0 17:03 pts/0    00:00:00 /xxxx/rke2/data/v1.34.4-rke2r1-0d52262ea640/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id eda29d7c7e12e4e3416458bbe3cffeb92781e7c8455b67d749bfb54860e3144a -address /run/k3s/containerd/containerd.sock
root      377420       1  0 17:03 pts/0    00:00:00 /xxxx/rke2/data/v1.34.4-rke2r1-0d52262ea640/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id 9e31fa56bee9d452280239e91103d4d920839f61742ce1ce112937a33b2618ef -address /run/k3s/containerd/containerd.sock
c
That's normal. Containers don't stop running when kubelet and containerd are stopped.
If you want all containers gone, drain the node first, or use the killall script.
m
got it, thanks