LAB 3.6 kubeadm init is failing at preflight checking: CRI v1 runtime API is not implemented for end

caishaoping

Hi There,

Need help on the direction where I should fix the issue during kubeadm init, it is failing at preflight check.

Thanks

Below is the command and error messages, I am also checked containerd:

1. kubeadm init command and error
   [email protected]:~$ sudo kubeadm init --kubernetes-version 1.23.1 --cri-socket=/var/run/containerd/containerd.sock --pod-network-cidr 192.168.0.0/16

[init] Using Kubernetes version: v1.23.1
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR CRI]: container runtime is not running: output: time="2023-02-08T18:54:32Z" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
To see the stack trace of this error execute with --v=5 or higher

2. containerd
   [email protected]:~$ sudo systemctl status containerd
   ● containerd.service - containerd container runtime
   Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2023-02-08 18:51:33 UTC; 5min ago
   Docs: https://containerd.io
   Main PID: 4010 (containerd)
   Tasks: 12
   Memory: 22.6M
   CGroup: /system.slice/containerd.service
   └─4010 /usr/bin/containerd

Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.032172706Z" level=info msg=serving... address=/run/containerd/containerd.sock.ttrpc
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.032224489Z" level=info msg=serving... address=/run/containerd/containerd.sock
Feb 08 18:51:33 ubuntu-focal systemd[1]: Started containerd container runtime.
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.035971041Z" level=info msg="containerd successfully booted in 0.050199s"
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.040234390Z" level=info msg="Start subscribing containerd event"
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.040605260Z" level=info msg="Start recovering state"
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.041018521Z" level=info msg="Start event monitor"
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.041189136Z" level=info msg="Start snapshots syncer"
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.041259453Z" level=info msg="Start cni network conf syncer"
Feb 08 18:51:33 ubuntu-focal containerd[4010]: time="2023-02-08T18:51:33.041364261Z" level=info msg="Start streaming server"
[email protected]:~$

caishaoping

Just a quick update: I followed the solution from below link to fix the issue: https://forum.linuxfoundation.org/discussion/862825/kubeadm-init-error-cri-v1-runtime-api-is-not-implemented

The key is: 1. sudo apt remove containerd
2. sudo apt-get update && sudo apt-get install -y containerd.io
3. sudo rm /etc/containerd/config.toml