kubeadm init fails when it can't find runc

at flag

I installed containerd and runc to /opt and I believe that's why kubeadm init is failing. Here is an error I see in the kubelet systemd log.

unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v2.task/ no such file or directory): exec: \"runc\": executable file not found in $PATH: unknown"" pod="kube-system/etcd-cp0" podUID=4b344419cbf991a1f149e60ac0841c36

How do I tell kubeadm where the runc binary is? Do I need to write a kubeadm-config.yaml file or can I generate one somehow? Thanks in advance.

mr.zog avatar
at flag
I added /opt/bin and /opt/sbin to my /etc/environment file.
mr.zog avatar
at flag
crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause finds no running containers.
at flag

Oh. I had removed apparmor. Now that I have reinstalled apparmor I can initialize my controlplane node.


Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.