run-containerd-runc-k8s.io Deactivated successfully

[raphael10-collab]

Just after logging-in I get in /var/log/syslog the message :

run-containerd-runc-k8s.io Deactivated successfully

Last login: Fri Nov  3 13:56:17 2023 
root@k8s-eu-1-master:~# 
root@k8s-eu-1-master:~# tail /var/log/syslog
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Listening on GnuPG cryptographic agent and passphrase cache.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Listening on debconf communication socket.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Listening on D-Bus User Message Bus Socket.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Reached target Sockets.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Reached target Basic System.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Reached target Main User Target.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Startup finished in 116ms.
Nov  3 14:26:19 k8s-eu-1-master systemd[1]: Started User Manager for UID 0.
Nov  3 14:26:19 k8s-eu-1-master systemd[1]: Started Session 70 of User root.
Nov  3 14:26:32 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.hRq2Ld.mount: Deactivated successfully.
root@k8s-eu-1-master:~# 

And this run-containerd-runc-k8s-io Deactivated successfully keeps going on, even if I do not do anything :

root@k8s-eu-1-master:~# tail /var/log/syslog
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Listening on debconf communication socket.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Listening on D-Bus User Message Bus Socket.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Reached target Sockets.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Reached target Basic System.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Reached target Main User Target.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Startup finished in 116ms.
Nov  3 14:26:19 k8s-eu-1-master systemd[1]: Started User Manager for UID 0.
Nov  3 14:26:19 k8s-eu-1-master systemd[1]: Started Session 70 of User root.
Nov  3 14:26:32 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.hRq2Ld.mount: Deactivated successfully.
Nov  3 14:28:02 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.WIeHEw.mount: Deactivated successfully.

Even after re-enabling and re-starting containerd :

root@k8s-eu-1-master:~# sudo systemctl enable containerd && systemctl start containerd
root@k8s-eu-1-master:~# 
root@k8s-eu-1-master:~# tail /var/log/syslog
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Reached target Main User Target.
Nov  3 14:26:19 k8s-eu-1-master systemd[543528]: Startup finished in 116ms.
Nov  3 14:26:19 k8s-eu-1-master systemd[1]: Started User Manager for UID 0.
Nov  3 14:26:19 k8s-eu-1-master systemd[1]: Started Session 70 of User root.
Nov  3 14:26:32 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.hRq2Ld.mount: Deactivated successfully.
Nov  3 14:28:02 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.WIeHEw.mount: Deactivated successfully.
Nov  3 14:30:32 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.iGjt5I.mount: Deactivated successfully.
Nov  3 14:31:02 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.cWuNCE.mount: Deactivated successfully.
Nov  3 14:32:00 k8s-eu-1-master systemd[1]: Reloading.
Nov  3 14:32:02 k8s-eu-1-master systemd[1]: run-containerd-runc-k8s.io-419083520012014e23f3b7c2c715181ca2d6e6f1a9f5476e39cddb815b62c8ef-runc.IWg7yu.mount: Deactivated successfully.

But containerd within nodes seem fine :

root@k8s-eu-1-master:~# kubectl get nodes -o wide
NAME                STATUS   ROLES           AGE    VERSION   INTERNAL-IP      EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
k8s-eu-1-master     Ready    control-plane   2d1h   v1.28.2   mm.mmm.mmm.mm    <none>        Ubuntu 22.04.3 LTS   5.15.0-88-generic   containerd://1.6.24
k8s-eu-1-worker-1   Ready    <none>          2d1h   v1.28.2   xx.xxx.xxx.xxx   <none>        Ubuntu 22.04.3 LTS   5.15.0-88-generic   containerd://1.6.24
k8s-eu-1-worker-2   Ready    <none>          2d1h   v1.28.2   yy.yyy.yyy.yyy   <none>        Ubuntu 22.04.3 LTS   5.15.0-88-generic   containerd://1.6.24
k8s-eu-1-worker-3   Ready    <none>          2d1h   v1.28.2   zz.zzz.zzz.zzz    <none>        Ubuntu 22.04.3 LTS   5.15.0-88-generic   containerd://1.6.24
k8s-eu-1-worker-4   Ready    <none>          2d1h   v1.28.2   ww.www.www.ww    <none>        Ubuntu 22.04.3 LTS   5.15.0-88-generic   containerd://1.6.24
k8s-eu-1-worker-5   Ready    <none>          2d1h   v1.28.2   pp.ppp.ppp.ppp   <none>        Ubuntu 22.04.3 LTS   5.15.0-88-generic   containerd://1.6.24

Is this the issue? :

root@k8s-eu-1-master:/usr/bin# ls -lah | grep runc
-rwxr-xr-x  1 root root    9.2M Sep 15 21:12 containerd-shim-runc-v1
-rwxr-xr-x  1 root root    9.2M Sep 15 21:12 containerd-shim-runc-v2
-rwxr-xr-x  1 root root    9.3M Sep 15 21:12 runc

Why does it happen? How to make it work?

[mehdi-aghayari]

I there any solution?