-
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
Hung downloading ISO (network contention with image pull) #4035
Comments
I have the same issue with minikube 1.0.0 running under kvm2 on Centos 7. I also run without issue using 0.35 (albeit with 0.31 docker-machine-kvm2 to avoid hidden config issue) so this appears to be a 1.0.0 issue. My Centos 7 is a VM running under VMWare Fusion on Mac (in case that makes any difference). |
I was able to work around by manually downloading All of the other downloads required during initial startup worked fine. It appears issue is limited to the initial download of the minikube ISO. |
This is happening to me on Fedora 29. |
Happening on Ubuntu 18.04 on kvm2. There is no way to get it to work I can find... totally busted. |
Thanks for the bug report! I believe that the root cause here is we're trying to download too much (7 Linux images simultaneously!), and some networks don't deal with this well. This should eventually unhang. You can test my root cause theory by using:
This will end up serializing the image downloads. |
I can confirm that on a faster network the hang does eventually clear and minikube starts successfully. |
Thanks for all the feedback! Here's the plan:
Look for a PR to be sent out in the next day on this. |
I've just installed virtualbox, kubectl and minikube... but when I run minikube start it freeze when is downloading the minikube iso smile minikube v1.0.0 on linux (amd64) I haven't found any solution so far... any suggestion? |
@locojuhi read above, running |
My minikube hangs when downloading the ISO using Minikube 1.0.0:
Tried with v0.35.0 and I do not have this issue:
The text was updated successfully, but these errors were encountered: