I tried extracting the checks in the entrypoint.sh file in https://github.com/kubernetes-sigs/cri-tools/pull/2069 as suggested as a reproducer in https://github.com/containerd/containerd/issues/13609#issuecomment-4767868455, but got no success.
I tried so by extracting the entrypoint.sh script from that PR, together with the setup-containerd.sh and wait-for-containerd.sh scripts and running them as standalone scripts in a resolute VM with containerd installed. We get no leak results: # ./entrypoint.sh Initializing container environment... Setting up containerd configuration in /etc/containerd... Enabling NRI plugin configuration (containerd main)... Setting up NRI socket directory... Setting up CNI networking in /etc/cni/net.d... Containerd and CNI setup complete. Starting containerd... Waiting for containerd to be ready (Socket: /run/containerd/containerd.sock, Log: /var/log/containerd.log)... Containerd is ready. Executing: Checking for leaked sandboxes... No leaked sandboxes. Checking for orphaned mounts... No orphaned mounts. Cleaning up containerd (PID: 8587).. I got the same results in a noble vm. Therefore, we must rely on user testing on their kubernetes clusters to verify this SRU. ** Bug watch added: github.com/containerd/containerd/issues #13609 https://github.com/containerd/containerd/issues/13609 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170996 Title: containerd fatal on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2170996/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
