5

whenever i am doing kubeadm init following error displayed can anyone help me here what i can do for this

[init] Using Kubernetes version: v1.26.1
[preflight] Running pre-flight checks
    [WARNING Swap]: swap is enabled; production deployments should disable swap unless testing the NodeSwap feature gate of the kubelet
error execution phase preflight: [preflight] Some fatal errors occurred:
    [ERROR CRI]: container runtime is not running: output: time="2023-01-26T18:54:12+05:30" 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

i tried restart containerd but not resolved chacked docker is running or not

Bhargav Patel
  • 1,098
  • 10
  • 23
Tukaram Waghmare
  • 75
  • 1
  • 3
  • 1
    I am also facing the same issue – Abhishek Dutta Feb 01 '23 at 04:13
  • 2
    By searching the web it appears this is an issue with the old containerd provided by Ubuntu 20. I solved it with the following steps (as root): 1. Set up the Docker repository as described in https://docs.docker.com/engine/install/ubuntu/#set-up-the-repository 2. Remove the old containerd:apt remove containerd 3. Update repository data and install the new containerd: apt update, apt install containerd.io 4. Remove the installed default config file: rm /etc/containerd/config.toml 5. Restart containerd: systemctl restart containerd The kubeadm init command worked fine afterwards. – Madhu Cheepati Feb 07 '23 at 00:41
  • 1
    @MadhuCheepati this worked for me, just by removing the config.toml and restart containerd. – Oussama Boumaad Feb 23 '23 at 08:55
  • @Tukaram Waghmare please check and let me know https://serverfault.com/questions/1118051/failed-to-run-kubelet-validate-service-connection-cri-v1-runtime-api-is-not-im/1127024#1127024 – Bhargav Patel Mar 24 '23 at 12:12
  • If you still dont have a solution, then try posting it on SuperUser site, – Rohit Gupta Mar 27 '23 at 11:33

0 Answers0