minikube: kubeadm init error running command: Process exited with status 1 (make error debuggable!)

Reverting to version 0.25.2 from 0.26 is a workaround for me on Windows.

I tried minikube delete and start and the same problem. However, downgrading it to version 0.25.2 works, thanks!

I faced the same issue on my laptop windows 10 minikube

minikube delete

then

minikube start

solved my issue

This seems to be network/firewall related to me. At work, if I’m connected to the secure company network, I get the exact same error as above no matter how many times I try. But If I switch to the insecure public network or I try at home I do not get the error and everything succeeds. By the way I am using minikube v0.30.0 with kubernetes version 1.12.0 on Windows 10 64bit v1709 with VirtualBox 5.2.8. Here is my configuration to start minikube:

Make sure all the .kube and .minikube folders are deleted and the VM is also removed before running this command:

minikube start --extra-config=apiserver.service-node-port-range=90-32000 \
    --kubernetes-version=v1.12.0 \
    --cpus 4 --memory 8192 --disk-size=50g

Starting local Kubernetes v1.12.0 cluster...
Starting VM...
Downloading Minikube ISO
 170.78 MB / 170.78 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubelet v1.12.0
Downloading kubeadm v1.12.0
Finished Downloading kubeadm v1.12.0
Finished Downloading kubelet v1.12.0
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.

With minikube v0.33, we’ve presented kubeadm errors directly to the console, removing the mystery and fulfilling this bug. If you run into any further kubeadm issues, please open a new bug. Thanks!

Same error on:

OS: OSX 10.14.1 Mojave VM Driver: Virtualbox Minikube version: v0.30.0

CMD:

sudo minikube delete && sudo minikube start 
\ --extra-config=apiserver.Authorization.Mode=RBAC  
\ --kubernetes-version=v1.13.0 
\ --bootstrapper=kubeadm 
\ --apiserver-ips 127.0.0.1 
\ --apiserver-name localhost 
\ --logtostderr 
\ --vm-driver=virtualbox

Log:

E1209 20:37:14.620167   97351 start.go:297] 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 coredns
 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 coredns

.: Process exited with status 1

Same issue using Ubuntu 18.04.1 LTS and kvm2 driver

0.25.2 works fine, 0.29 does not.

Getting the same error on OS: Windows 7 VM Driver: Oracle Virtualbox v5.2.8 Minikube version: v0.26.0

Just found related issue that solved my problem: https://github.com/kubernetes/minikube/issues/2696

Same issue on Windows 10

Starting cluster components...
E0328 21:54:51.600728    7358 start.go:276] 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
================================================================================
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]:

After rerunning now i got this

`

Starting cluster components...
E0412 18:04:43.797557   34012 start.go:281] Error restarting cluster:  restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition
================================================================================
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]:
y

I just experienced this on macOS 10.12.6, minikube v0.25.0, kubectl version:

Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:28:34Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}

@shresthsuman I’m running kubernetes in a Linux Mint. I wasn’t referring to the minikube hardware, but to the host hardware, Mint in my case. The thing is that I have Windows and didn’t want to install a clean Mint version in a hard drive, so I created a virtual machine using vmware instead. Is the hardware of that vm I was referring to.

I’m using virtualbox driver in a Linux environment

I was having the very same issue, running a Mint guest VMware machine on a Win10 host. That VM had 2GB and 2 CPUs. In Mint, I ran this command journalctl -f when minikube was starting and noticed an error of virtual box not having enough memory. I then added 4 more GB to the RAM, and 2 more cores, and that seemed to solve the issue. It turned out to be a lack of hardware resources

why is this still an issue? It is rendering minikube useless on arguably an important platform. Is it not worthy of someone trying to fix?

I’m curious… Is anyone looking into this? It seems all the recent messages are just further reports of it not working. I would help out myself, but I lack the knowledge to tackle this.

I am also seeing this issue.

Ubuntu 18.10 64bit kernel: 4.18 Minikube 0.29

christian@robo-beaver ~ $ minikube start --vm-driver=kvm2 --cpus=2 --memory=4096 --disk-size=45GB --extra-config=apiserver.Authorization.Mode=RBAC
There is a newer version of minikube available (v0.30.0).  Download it here:
https://github.com/kubernetes/minikube/releases/tag/v0.30.0

To disable this notification, run the following:
minikube config set WantUpdateNotification false
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Downloading Minikube ISO
 170.18 MB / 170.18 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.10.0
Downloading kubelet v1.10.0
Finished Downloading kubelet v1.10.0
Finished Downloading kubeadm v1.10.0
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E1022 12:13:27.600279    9609 start.go:297] 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
================================================================================

I even went so far as to remove the minikube binaries, and ~/.minikube directory and install from scratch. Same problem.

This concludes that this is a real problem and not related to old crud left behind.

This seems to be a general case of kubeadm failures, for which we don’t yet provide any additional helpful error messages. If someone sees this again, please attach the output from “minikube ssh” running the following:

sudo journalctl -u kubelet sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks

as well as:

cat /var/lib/kubeadm.yaml

Thanks!

Get the same issue too, the logs is as following: OS: OS X 10.12.3 Minikube: 0.26.0 VM: VirsualBox

minikube start --registry-mirror=https://registry.docker-cn.com 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… E0417 18:23:34.065553 12866 start.go:281] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition E0417 18:23:40.334590 12866 util.go:151] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: read tcp 192.168.3.2:55296->216.58.200.234:443: read: connection reset by peer