Error starting cluster: kubeadm init error (Process exited with status 1, no root cause)

[lhui8023]

macOS 10.13.6
VirtualBox-5.2.16-123759-OSX
minikube:v0.28.2

[localhost:v1.10.0 leihui$ minikube start
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...

Setting up kubeconfig...

Starting cluster components...
E0802 14:11:33.136236 886 start.go:300] Error starting cluster: kubeadm init error
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns
running command: : running command:
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns

.: Process exited with status 1

An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
minikube config set WantReportErrorPrompt false

Please enter your response [Y/n]:

[erickpearson]

I'm getting the same exact error message on same minikube version, although I'm using hyperkit v0.20171204-60-g0e5b6b

I haven't dug too deep yet, did you find anyway to get your local cluster started?

[lhui8023]

@erickpearson
you can try it $minikube start --vm-driver=hyperkit --bootstrapper=localkube

[lhui8023]

@erickpearson
$minikube stop
$minikube delete && rm -rf ~/.minikube && rm -rf ~/.kube
$minikube start --vm-driver=hyperkit --bootstrapper=localkube
retry

[erickpearson]

@lhui8023 running the localkube bootstrapper worked. However it does suggest that this is deprecated and consider moving to kubeadm bootstrapper which is what was having trouble initializing. Thanks for the help, I'll work with this for now.

[redbearder]

@erickpearson @lhui8023 I have same issue with you, although I have fix that with same solution but I want to know the root cause and have a long term solution about that

[rfc1459]

After a round of git bisect between v0.28.0 (good) and v0.28.2 (bad), it seems that 81440fe broke k8s 1.10 deployments. k8s 1.11 works fine.

Host environment:

• OS: Ubuntu 18.04
• Hypervisor: VirtualBox 5.2.18-124319
• Behind corporate proxy (if that makes any difference)

[fabiand]

Using minikube v0.28.0 with Ubuntu Xenial 16.04, non driver and K8s 1.10 or 1.11 does not work form me.

[jkremser]

0.28.0 is also broken on fedora 28:

minikube start --kubernetes-version="v1.11.0" --vm-driver=kvm2 

in the log:

Aug 29 14:17:13 minikube kubelet[2458]: F0829 14:17:13.195876    2458 server.go:262] failed to run Kubelet: unable to load bootstrap kubeconfig: stat /etc/kubernetes/bootstrap-kubelet.conf: no such file or directory

Although, I was lucky with

minikube start --kubernetes-version="v1.10.0" --vm-driver=kvm2 --extra-config=apiserver.v=4 --bootstrapper=localkube

[fabiand]

There seem to be some deprectaion warnings in the kubelet.

[tstromberg]

closing as a dupe of #2493

[fabiand]

@tstromberg dupe of itself?

I'm not sure what now the correct bug to follow is

[tstromberg]

@fabiand - Whoops. Thanks for catching my mistake. #2493 is the issue I've duped this one against.

[haf]

This is not a duplicate, because the error message unable to load bootstrap kubeconfig does not exist in #2493 but it exists in this issue.