Minikube start throwing error Failed to enable unit: Unit file cri-docker.socket does not exist.

[Abhijitrb]

What Happened?

loadtest@COMP-4928-1 ~]$ minikube start
\U0001f604 minikube v1.26.0 on Redhat 8.2
\u2728 Using the none driver based on existing profile
\U0001f44d Starting control plane node minikube in cluster minikube
\U0001f504 Restarting existing none bare metal machine for "minikube" ...
\u2139\ufe0f OS release is Red Hat Enterprise Linux 8.2 (Ootpa)

\u274c Exiting due to RUNTIME_ENABLE: sudo systemctl enable cri-docker.socket: exit status 1
stdout:

stderr:
Failed to enable unit: Unit file cri-docker.socket does not exist.

Attach the log file

Operating System

Redhat/Fedora

Driver

No response

[spowelljr]

Hi @Abhijitrb, thanks for reporting your issue with minikube.

This is a duplicate of #14410

You can read this comment (#14410 (comment)) for more info. But the quick answer is:

Kubernetes v1.24 dropped support for Dockershim, so if you want to use the combination of the none driver, Kubernetes v1.24+, and the Docker container runtime you'll need to install cri-dockerd on your system, as listed in our requirements page.

So follow these install instructions and your issue will be resolved: https://github.com/Mirantis/cri-dockerd#build-and-install

I'm going to close this issue to prevent duplicates, but if you have follow up questions please ask them in #14410, thanks

[Abhijitrb]

Thank you Steven for your comments!

I followed that solution link #14410. In that I tried to install cri-dockerd
After executing these commands

Run these commands as root

###Install GO###
wget https://storage.googleapis.com/golang/getgo/installer_linux
chmod +x ./installer_linux
./installer_linux
source ~/.bash_profile
cd cri-dockerd
mkdir bin
go get && go build -o bin/cri-dockerd
mkdir -p /usr/local/bin
install -o root -g root -m 0755 bin/cri-dockerd /usr/local/bin/cri-dockerd
cp -a packaging/systemd/* /etc/systemd/system
sed -i -e 's,/usr/bin/cri-dockerd,/usr/local/bin/cri-dockerd,' /etc/systemd/system/cri-docker.service
systemctl daemon-reload

Post execution of "systemctl enable cri-docker.service" i am getting below error output
Failed to enable unit: Unit file cri-docker.service does not exist

Not sure why I see above error even though cri-docker.service is present.

Any thoughts on this?

[spowelljr]

Are you running these commands as root? ie. sudo systemctl enable cri-docker.service that's my first guess, let me know and we can go from there, thanks.

[Abhijitrb]

Yes I am running these commands as root. I tried with "sudo systemctl enable cri-docker.service" still i can see same error
Failed to enable unit: Unit file cri-docker.service does not exist

Till "systemctl daemon-reload" this point there were no issues

Not able to understand those services are present still why enable cri-docker.service not works!

[Abhijitrb]

This issue got resolved now..After that when I re-executed minikube start --driver=none a new issue has been encountered
Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1
stdout:

stderr:
sudo: crictl: command not found

After this I again tried to install crictl package however not worked!

Same issue coming

[spowelljr]

What happens when you try to run sudo crictl?

[Abhijitrb]

On running "sudo crictl" not getting any response
sudo: crictl: command not found

However I searched for crictl package and found link for crictl installation.
https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md

I installed but no success so far. Not able to figure out why this error coming!

here is the complete error message::

**Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1
stdout:

stderr:
sudo: crictl: command not found**

[yongqiangG]

I have the same problem.

X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1
stdout:

stderr:
sudo: crictl: command not found