minikube: Minikube fails for Kubernetes v1.8.0 using kubeadm bootstrapper
Trying to run the freshly released Kubernetes v1.8.0 does not work for me:
$ minikube start --cpus 4 --memory 4096 --kubernetes-version v1.8.0 --vm-driver kvm --bootstrapper kubeadm
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E0929 12:15:14.339869 23029 start.go:261] Error starting cluster: kubeadm init error running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks: Process exited with status 1
Choosing v1.7.6 or v1.7.7 works fine on the same system:
$ minikube start --cpus 4 --memory 4096 --kubernetes-version v1.7.7 --vm-driver kvm --bootstrapper kubeadm
Starting local Kubernetes v1.7.7 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.7.7
Downloading kubelet v1.7.7
Finished Downloading kubelet v1.7.7
Finished Downloading kubeadm v1.7.7
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
$ kubectl get nodes
NAME STATUS AGE VERSION
minikube Ready 1m v1.7.7
Environment: minikube version: v0.22.2
OS:
NAME="Ubuntu"
VERSION="17.10 (Artful Aardvark)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Artful Aardvark (development branch)"
VERSION_ID="17.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=artful
UBUNTU_CODENAME=artful
VM driver:
"DriverName": "kvm",
ISO version
"ISO": "/home/webwurst/.minikube/machines/minikube/boot2docker.iso",
"Boot2DockerURL": "file:///home/webwurst/.minikube/cache/iso/minikube-v0.23.4.iso",
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 7
- Comments: 22 (7 by maintainers)
Commits related to this issue
- Minikube start workaround https://github.com/kubernetes/minikube/issues/2018#issuecomment-335405784 — committed to metacoma/aws-minikube by deleted user 7 years ago
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 https://github.com/kubernetes/minikube/pull/1985
It’s failing on Windows 10 for me:
@LiliC thanks, I was just trying until I run minikube delete from your post, and now it works.
@uromahn Works normally for me on a Mac just fine:
Have you tried upgrading
minikubeitself, the version I am using isv0.22.3.Right, but I think that is for the default
localkubebootstrapper. withkubeadmyou should be able to choose freely among released Kubernetes versions. And in fact it works fine for me withv1.7.6andv1.7.7as stated above, although these are not listed withminikube get-k8s-versions. But thanks for the heads-up 😃Why have you closed this ticket without really explaining the root cause, why we get the
proc exit status 1FYI: the problem still exist - #3455
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
--kubernetes-version=v1.9.4, but not working. I can only start with--bootstrapper=localkube, other bootstrapper params never work…Had the same issue as @sjezewski, ^, was resolved by deleting the cluster and starting again.
@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. 😃