❌ Exiting due to RUNTIME_ENABLE: sudo systemctl enable cri-docker.socket: exit status 1 stdout: stderr: Failed to execute operation: No such file or directory

[joshua143]

What Happened?

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

stderr:
Failed to execute operation: No such file or directory

Attach the log file

minikube logs --file=logs.txt

Operating System

Other

Driver

Docker

[spowelljr]

Hi @joshua143, just double checking that you're using the Docker driver.

If that's the case you likely created your current minikube cluster with a previous version of minikube and then you updated the minikube binary to v1.26.0 which tries to start cri-docker, but because your cluster was created with a previous version cri-docker isn't installed.

This should be easily resolvable by running minikube delete --all and then try starting minikube again, thanks

[robrich]

Just hit this as well. I wish this issue was called out on the release's download page.

[afbjorklund]

It is theoretically possible to install cri-dockerd, when upgrading an old installation

[spowelljr]

@joshua143 & @robrich are both of you using the docker driver? Or are you perhaps using the none driver?

[spowelljr]

Going to close this issue to centralize these duplicated cri-docker issues in #14410. If you have any further questions or comments please leave them in #14410, thank you.

[robrich]

I'm using the hyperv driver.