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)
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:
If this doesnโt fix it, do you mind adding the output of
minikube start --alsologtostderr -v=8after 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!!