-
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
Minikube start fails on 0.26.0, 0.26.1, 0.27.0, 0.28.0 (Win 10 + VirtualBox) #2818
Comments
The root of this problem appears to be related to the minikube profile feature and its current breakage is covered in #2717 If you notice above the log reports a node name of "minikube-sonarqube" instead of the default "minikube". This is because I had been previously working with a profile name set with If I switch the profile to the default Since version 0.26.0, 0.26.1 and now 0.27.0 there is a definite problem with using profiles and that is confirmed with #2717. To replicate the error:
and you will see:
Workaround: The above error does not occur with version 0.25.2 as profiles appear to work with that previous release. Perhaps this can be closed as supportive information for #2717? (An enhancement could be to change the start message from "Starting local Kubernetes v1.10.0 cluster..." to "Starting local Kubernetes v1.10.0 cluster with profile [profile name]...") |
@javajon same issue with me,This problem exists in v0.26.x and later versions。 |
Same issue on mac osx 10.13.4 only with minikube start --vm-driver=hyperkit --bootstrapper=localkube works |
Minikube version 0.28.0 produces same error:
|
As found also in #2574 the use of deprecated |
Hi @javajon, I just to make sure that run Minikube v0.28.0 on Windows 10, I also tried to use Hyper-V and Virtualbox(5.2.12) driver to start VM, but it can be performed successfully. Hyper-V snapshots: Virtualbox snapshots: Could you remove the config dir and try again? $ rm -r $HOME/.minikube
$ minikube.exe start
|
Dupe of #2574 |
BUG REPORT
Environment:
Minikube version: v0.27.0
What happened:
Minikube status does report running:
However, pods remain forever pending
What you expected to happen:
No errors when starting
Pods should be starting
minikube dashboard should function
How to reproduce it (as minimally and precisely as possible):
minikube start
on above system.Output of
minikube logs
(if applicable):Possible notable excerpts from: VBoxHardening.log
Anything else do we need to know:
Something went wrong after version 0.25.2
Five other colleagues I work with have also reported similar problems on Windows 10 with VirtualBox. They have all reverted back to 0.25.2. I was hoping 0.27.0 would resolve the issue.
Tried minikube delete and a restart. Deleted all of VirtualBox and .kube .minikube and .VirtualBox files. Fresh install of VirtualBox, and minikube and still same problem on versions 0.26.0, 0.26.1 and 0.27.0
Workaround: Revert minikube.exe to version 0.25.2 and all returns to normal working order.
The text was updated successfully, but these errors were encountered: