Forum archive › Kubernetes & Helm Charts

[ERROR CRI]: container runtime is not running: / msg=\"unable to determine runtime API version\"

Read-only archive. These discussions are from Tracston's earlier technical forum and are kept online because the answers are still useful. New replies are closed. Need help with something like this? Talk to us.

Question 12 Jul 2022

Problem

User gets the following error when trying to start / restart kubernetes

[preflight] Running pre-flight checks

error execution phase preflight: [preflight] Some fatal errors occurred:

[ERROR CRI]: container runtime is not running: output: time="2022-07-12T14:04:08+03:00" level=fatal msg="unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""

, error: exit status 1

Solution

Run the following commands to fix the issu

rm /etc/containerd/config.toml
systemctl restart containerd

Initialize Kubernetes

kubeadm init

Reply 1 12 Jul 2022

If this solution doesnt helps change the docker version from docker to docker-ce

rpm -e docker-common-1.13.1-209.git7d71120.el7.centos.x86_64 docker-1.13.1-209.git7d71120.el7.centos.x86_64 docker-client-1.13.1-209.git7d71120.el7.centos.x86_64
sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo yum install docker-ce

systemctl start docker

Need this fixed properly?

We do this for a living.

Kubernetes, DevOps and platform engineering, delivered in days — not another weekend lost to a stack trace.

Start a project →