minikube: Incompatible hyperkit driver causes "Waiting for SSH access ..." hang after macOS restart

After rebooting my computer, any attempts to restart my Minikube cluster do not work. I get the following output:

๐Ÿ˜„  minikube v0.35.0 on darwin (amd64)
๐Ÿ’ก  Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
๐Ÿ”„  Restarting existing hyperkit VM for "minikube" ...
โŒ›  Waiting for SSH access ...

And it just sits there, never even timing out no matter how long I wait.

How to replicate:

minikube start --cpus=4 --memory=4096 --disk-size=30g --vm-driver=hyperkit --kubernetes-version=v1.10.12 --extra-config=apiserver.authorization-mode=RBAC

I am using macOS Mojave Version 10.14.3. Hereโ€™s my output from minikube logs:

๐Ÿ’ฃ  command runner: getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp 192.168.64.11:22: connect: operation timed out

๐Ÿ˜ฟ  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
๐Ÿ‘‰  https://github.com/kubernetes/minikube/issues/new

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 15 (4 by maintainers)

Most upvoted comments

OK. That sounds like a bug with the hyperkit driver. Do you mind running this for me?

% ls -lad $(type -a docker-machine-driver-hyperkit)

Assuming it doesnโ€™t say 27779836 bytes long, Iโ€™m curious if upgrading to the latest driver version fixes the situation:

% curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-hyperkit \
&& sudo install -o root -g wheel -m 4755 docker-machine-driver-hyperkit /usr/local/bin/

If this doesnโ€™t fix it, do you mind adding the output of minikube start --alsologtostderr -v=8 after a reboot?

We have a long-standing issue where we donโ€™t have control over which hyperkit driver is installed on machines, and Iโ€™m hoping this is the evidence we need to finally fix the issue.

I ran into the same issue and this can be solved by a simple command below:

minikube delete && minikube start

Hope that solves problems of many people!!