Minikube fails for Kubernetes v1.8.0 using kubeadm bootstrapper #2018
Comments
|
@webwurst You can get a list of supported kubernetes versions by running; |
|
Right, but I think that is for the default |
|
Could be #1996 |
|
I have a PR to fix this, but I was reworking it to add args to all components, I'll try to get it pushed later today #1985 |
|
Just as an add-on: I am trying to start a k8s v1.5.7 using the same method and are seeing the exact same error message. Will PR #1985 also fix this issue or is there another "special fix" needed? |
|
It seems to be working with minikube 0.22.3 here: However, I don't know the level of support for the new kubeadm bootstrapper. Is it possible that aiming for locakube to support 1.8.0 for now would be less disruptive? |
|
This issue needs to be re-opened since the kubeadm bootstrapper is not working on Mac OS X! When I started it trying with k8s v1.5.7 I am getting the following error message: After that, when I try to start it with any other k8s version, e.g. v1.8.0 or v1.7.7 it "hangs" after the message "Starting cluster components..." |
|
@uromahn Works normally for me on a Mac just fine: Have you tried upgrading |
|
@lilic thanks, I was just trying until I run minikube delete from your post, and now it works. |
|
It's failing on Windows 10 for me: |
|
@lilic It is working for me with the default virtualbox vm-driver. However, it still fails with xhyve on my Mac. I'd rather prefer to use xhyve since it is "leaner" than running a virtualbox VM. Also, yes, I am using the latest minikube version v0.22.3. :) |
|
Trying it too on my Linux machine ( Arch Linux, with Kernel 4.13.11 ) I get this error: by running this command and it hangs there. Any idea what to do? //EDIT: Solved using directly |
|
This is fixed at HEAD and will be in the next version of minikube |
|
This is still failing for me on Windows 10 64-bit Creators Update with Minikube 0.24.1 and VirtualBox 5.2.2: I deleted the cluster and tried again, but I still get the same error. I tried k8s v1.8.0, but still get the same error: |
|
This still seems to be an issue. I'm on ubuntu 16.04 w minikube Running w/o the none user flag produces a different error: |
|
Had the same issue as @sjezewski, ^, was resolved by deleting the cluster and starting again. |
This should definitely be added to the doc. :) |
|
Is there any better solution than deleting and restarting, which doesn't work for me? I have the same issue with @sjezewski on Ubuntu 16.04, no matter with kvm2/virtualbox/None driver. I also tried specifying |
|
Why have you closed this ticket without really explaining the root cause, why we get the FYI: the problem still exist - #3455 |
|
minikube start
! Ignoring --vm-driver=virtualbox, as the existing "minikube" VM was created using the hyperv driver.
X Unable to start VM: start: exit status 1 minikube status The values for minikube status remains empty. What would be the problem for this? How do I resolve it. |
|
minikube stop
X Unable to stop VM: Temporary Error: Stop: minikube: exit status 1
How do I resolve this. Minikube is either starting nor stopping. |
Trying to run the freshly released Kubernetes
v1.8.0does not work for me:Choosing
v1.7.6orv1.7.7works fine on the same system:Environment:
minikube version: v0.22.2
The text was updated successfully, but these errors were encountered: