Closed EHJ-52n closed 2 years ago
I suspect you had an existing Minikube cluster, using old image that didnt have cri dockerd
does deleting minikube and starting a new one fix the problem?
Hi @EHJ-52n, following up with what @medyagh said. minikube v1.26.0 introduced cri-dockerd
however, since you're using the updated binary with a cluster created with a previous version it's trying to start cri-dockerd
but your cluster doesn't actually have that service installed.
Try running minikube delete --all
and then try starting minikube again and your issue should be resolved, thanks!
@spowelljr Your piece of advice was working as you can see in the following:
~ minikube status
minikube
type: Control Plane
host: Stopped
kubelet: Stopped
apiserver: Stopped
kubeconfig: Stopped
~ minikube start --kubernetes-version=stable
๐ minikube v1.26.0 on Ubuntu 21.10
โจ Using the docker driver based on existing profile
๐ Starting control plane node minikube in cluster minikube
๐ Pulling base image ...
๐ Restarting existing docker container for "minikube" ...
โ Exiting due to RUNTIME_ENABLE: stat /var/run/cri-dockerd.sock: Process exited with status 1
stdout:
stderr:
stat: cannot stat '/var/run/cri-dockerd.sock': No such file or directory
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ โ
โ ๐ฟ If the above advice does not help, please let us know: โ
โ ๐ https://github.com/kubernetes/minikube/issues/new/choose โ
โ โ
โ Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. โ
โ โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
~ minikube delete --all
๐ฅ Deleting "minikube" in docker ...
๐ฅ Removing /home/eike/.minikube/machines/minikube ...
๐ Removed all traces of the "minikube" cluster.
๐ฅ Successfully deleted all profiles
~ minikube start --kubernetes-version=stable
๐ minikube v1.26.0 on Ubuntu 21.10
โจ Automatically selected the docker driver. Other choices: ssh, qemu2 (experimental)
๐ Using Docker driver with root privileges
๐ Starting control plane node minikube in cluster minikube
๐ Pulling base image ...
> gcr.io/k8s-minikube/kicbase: 385.99 MiB / 386.00 MiB 100.00% 8.41 MiB p/
> gcr.io/k8s-minikube/kicbase: 0 B [_________________________] ?% ? p/s 40s
๐ฅ Creating docker container (CPUs=2, Memory=7900MB) ...
๐ณ Preparing Kubernetes v1.24.1 on Docker 20.10.17 ...
โช Generating certificates and keys ...
โช Booting up control plane ...
โช Configuring RBAC rules ...
๐ Verifying Kubernetes components...
โช Using image gcr.io/k8s-minikube/storage-provisioner:v5
๐ Enabled addons: storage-provisioner, default-storageclass
๐ Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
~ minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
~ minikube version
minikube version: v1.26.0
commit: f4b412861bb746be73053c9f6d2895f12cf78565
Glad that resolved your issue @EHJ-52n!
What Happened?
Attach the log file
Operating System
Ubuntu
Driver
Docker