In a kubernetes cluster the calico pod on the worker node is stuck in state “Init: 0/2” when added to the cluster.
On the control node, however, the calico node pod stays in running state.
The cluster runs on Microk8s v1.31/stable on top of Ubuntu Server 24.04 on both the control node and the worker node.
In the kubernetes dashboard i can see the following error in the failing calico pod:
(combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: failed to create shim task: failed to mount rootfs component &{overlay overlay [workdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/237259/work upperdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/237259/fs lowerdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1/fs]}: invalid argument: unknown
Why can’t the calico pod be initialised on the worker node?
Can someone please suggest some possible reason for the problem?
Is something missing in the configuration?
Thx for the question.
Calico is the CNI used in microk8s.
As you can see below the calico pod on the worker node is stuck in init state. The question is why.