-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible hyperkit driver causes "Waiting for SSH access ..." hang after macOS restart #3823
Comments
Thank you for the bug report! Sorry that minikube didn't work for you. I tested your command-line on macOS 10.4.3, but wasn't able to reproduce it. This could be a few different things:
Do you mind supplying a few commands so that we can help figure out what's going on?
If so, I'm curious what version of the ISO your existing build has. You can find out by running:
If neither work, do you mind running the following commands:
Thanks! |
Hi, thanks for the quick response! Starting a new minikube profile works fine. The only issue is when I shut off my computer, then attempt to restart an existing cluster next time. The output from the
|
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 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. |
Yes - upgrading to the latest driver version seems to have solved my problem! I'll test it out again on my next reboot and report back. |
Still working after my latest reboot. Looks like that did the trick. Thanks for your help! |
Thanks! I'm going to keep this open for others who run into this issue, at least until we have a way to always guarantee the appropriate hyperkit version. |
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!! |
That works, but it's not really a viable solution when you have a lot of things in your cluster. For us, it took a long time to reinstall everything in the cluster so having to delete it every time was a huge problem. |
I think I'm running into the same issue, and it's the same as #3542. I haven't been able to solve it with |
I've run into this problem, too. MacOS 10.14.4 (up-to-date, as of today) minikube delete && minikube start didn't fix the problem. curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-hyperkit |
Even i am facing similar problem , but it didn't resolved with any of above solutions. I have tried by installing Virtual box with that also it didn't worked. below is the response when i triggered with Virtualbox
🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ... 😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: Basically i have tried with xhvye, hyperkit, VirtualBox but none of these didn't worked |
i just do this, and it works well
|
Marking as fixed in v1.0, so long as the appropriately up to date hyperkit driver has been installed:
|
hi all, just a quick follow-up from my experience that points to this not being fully resolved in v1.0. i'm running: when minikube is shut down cleanly (i.e. perhaps some cleanup checks need to be added a start up. |
I am facing the same issue. can anyone help please. I have already tried the above solution for installing the latest hyperkit but still the issue persists. minikube version - v1.9.2 |
After rebooting my computer, any attempts to restart my Minikube cluster do not work. I get the following output:
And it just sits there, never even timing out no matter how long I wait.
How to replicate:
I am using macOS Mojave Version 10.14.3. Here's my output from
minikube logs
:The text was updated successfully, but these errors were encountered: