minikube doesn't start on Macbook Pro

[marcwegman]

What Happened?

Bash-3.2$ minikube start --driver=docker
😄 minikube v1.37.0 on Darwin 15.6.1 (arm64)
✨ Using the docker driver based on user configuration

💣 Exiting due to PROVIDER_DOCKER_NOT_RUNNING: "docker version --format -:" exit status 1: Cannot connect to the Docker daemon at unix:///Users/marc/.docker/run/docker.sock. Is the docker daemon running?
💡 Suggestion: Start the Docker service
📘 Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/

Bash-3.2$ minikube start --driver=docker
E0915 15:58:59.108657 55364 cloud_events.go:60] unable to write to ..../.minikube/profiles/minikube/events.json: open .../.minikube/profiles/minikube/events.json: operation not permitted
😄 minikube v1.37.0 on Darwin 15.6.1 (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.48 ...
💾 Downloading Kubernetes v1.34.0 preload ...
> preloaded-images-k8s-v18-v1...: 332.38 MiB / 332.38 MiB 100.00% 6.47 Mi
> gcr.io/k8s-minikube/kicbase...: 450.06 MiB / 450.06 MiB 100.00% 7.08 Mi
🔥 Creating docker container (CPUs=2, Memory=6100MB) ...
✋ Stopping node "minikube" ...
🛑 Powering off "minikube" via SSH ...
🔥 Deleting "minikube" in docker ...
🤦 StartHost failed, but will try again: save: open /.../minikube/config.json.tmp3242490471: operation not permitted
🤷 docker "minikube" container is missing, will recreate.
🔥 Creating docker container (CPUs=2, Memory=6100MB) ...
😿 Failed to start docker container. Running "minikube delete" may fix it: recreate: creating host: create: saving: open /Users/marc/.minikube/machines/minikube/config.json.tmp1092399897: operation not permitted

❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: recreate: creating host: create: saving: open .../.minikube/machines/minikube/config.json.tmp1092399897: operation not permitted

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 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. │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

Attach the log file

....

Operating System

macOS (Default)

Driver

Docker

[marcwegman]

Logfile could not be made:
E0915 16:30:35.320694 61792 logs.go:261] failed to output audit logs: failed to create audit report: failed to open the audit log: open /Users/marc/.minikube/logs/audit.json: operation not permitted

❌ 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
stdout:

stderr:
Error response from daemon: {"message":"No such container: minikube"}

[nirs]

Maybe your ~/.minikube directory is owned by root?
Did you run the minikube as root by mistake before?

Check:

tree -pugh ~/.minikube

But on macOS using docker driver is pointless. You must have a vm so you better use a vm driver like vfkit which is also the preferred driver on macOS since minikube 1.36.0.

Try:

brew install vfkit
minikube start --driver vfkit

[marcwegman]

Thank you,

I will have a loot whether this works out for me.

[marcwegman]

The approach with:
brew install vfkit
minikube start --driver vfkit

works for me.

Thanks

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

Details

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.