Minikube Won't start on M3 mackbook

[ivgenyr]

What Happened?

When trying to run a minikube cluster, i end up with the following error:

minikube start --driver=docker --container-runtime=containerd --docker-opt="platform=linux/arm64"
😄  minikube v1.34.0 on Darwin 14.7 (arm64)
✨  Using the docker driver based on user configuration
📌  Using Docker Desktop driver with root privileges
👍  Starting "minikube" primary control-plane node in "minikube" cluster
🚜  Pulling base image v0.0.45 ...
🔥  Creating docker container (CPUs=2, Memory=7789MB) ...
🤦  StartHost failed, but will try again: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85 -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85' locally
gcr.io/k8s-minikube/kicbase@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85: Pulling from k8s-minikube/kicbase
70b0e931bdc1: Pulling fs layer
70b0e931bdc1: Verifying Checksum
70b0e931bdc1: Download complete
70b0e931bdc1: Pull complete
Digest: sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85
docker: cannot overwrite digest sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85.
See 'docker run --help'.

🤷  docker "minikube" container is missing, will recreate.
🔥  Creating docker container (CPUs=2, Memory=7789MB) ...
😿  Failed to start docker container. Running "minikube delete" may fix it: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85 -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85' locally
gcr.io/k8s-minikube/kicbase@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85: Pulling from k8s-minikube/kicbase
Digest: sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85
docker: cannot overwrite digest sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85.
See 'docker run --help'.


❌  Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85 -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.45@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85' locally
gcr.io/k8s-minikube/kicbase@sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85: Pulling from k8s-minikube/kicbase
Digest: sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85
docker: cannot overwrite digest sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85.
See 'docker run --help'.

Attach the log file

Unable to dump logs:

Exiting due to GUEST_STATUS: Unable to get control-plane node minikube host status: state: unknown state "minikube": docker container inspect minikube --format={{.State.Status}}: exit status 1

Operating System

macOS (Default)

Driver

Docker

[AmarNathChary]

docker: cannot overwrite digest sha256:81df288595202a317b1a4dc2506ca2e4ed5f22373c19a441b88cfbf4b9867c85.

In my opinion this suggests Docker may have cached the image or is encountering a conflict when trying to pull the specified image digest.

[AmarNathChary]

Try remove the conflicting cached image and try pulling it again.

[AmarNathChary]

also try delete any existing Minikube setup and start a fresh instance. this might resolve issue

[merlixelastic]

I'm facing this error too very recently

[Thom-x]

I had the same issue.
I'm mounting docker images into minikube with a dedicated volume to be able to cache images between minikube delete/start.

 --mount --mount-string minikube-docker-volume:/var/lib/docker

The issue seems to involve gcr.io/k8s-minikube/storage-provisioner image being pulled again with a conflict.
Workaround, was to delete all images related to minikube inside that volume.

docker run  -v minikube-docker-volume:/var/lib/docker --privileged -d --name dind-test docker:dind
docker exec -it dind-test /bin/sh
docker images | grep minikube
docker rmi <image from previous command>