kubeadm init error running command: Process exited with status 1 (make error debuggable!) #2493
Labels
co/kubeadm
Issues relating to kubeadm
co/virtualbox
kind/bug
Categorizes issue or PR as related to a bug.
Comments
|
Also failing on Windows 10 1709 64-bit and VirtualBox 5.2.6 here, but for a different reason: |
r2d4
added
drivers/virtualbox/windows
co/kubeadm
|
I just experienced this on macOS 10.12.6, minikube v0.25.0, |
|
Seems related to #2131. |
|
Faced this issue on arch linux |
|
Same issue on Windows 10 After rerunning now i got this ` |
|
Hi. I am also having the same issue when trying to install All-in-one-node Kubernetes cluster with minikube. It seems like an issue when starting the cluster. Below are the details: I am not sure if it is related or not but running kubectl version command returns |
|
Hi, getting exactly the same issue as described by @asifmammadov |
|
Getting the same error on Just found related issue that solved my problem: #2696 |
|
Get the same issue too, the logs is as following: minikube start --registry-mirror=https://registry.docker-cn.com |
|
Me too, same issues on unhealthy kubeadm: v1.10.0 [kubelet-check] It seems like the kubelet isn't running or healthy. |
|
I faced the same issue on my laptop windows 10 minikube minikube delete then minikube start solved my issue |
|
Reverting to version 0.25.2 from 0.26 is a workaround for me on Windows. |
|
Yes works when downgrading minikube to 0.25.2, hope the issues will be fixed in 0.26 soon. |
|
I tried minikube delete and start and the same problem. However, downgrading it to version 0.25.2 works, thanks! |
|
@asifmammadov Thanks it works for me ! |
|
Same issue Workaround use minikube 0.25.2 work! |
|
Got same issue on: You should explicit your --vm-driver, minikube start --vm-driver=virtualboxworks fine! |
|
I followed the approach suggested by @3miliomc and it worked! 👍
O/S: Windows 10 Pro |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
the
lifecycle/stale
tstromberg
changed the title
|
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 as well as: cat /var/lib/kubeadm.yaml Thanks! |
tstromberg
removed
the
lifecycle/stale
True. I have tried it many which ways. Start. Ctrl+C. Force shut down with virtual box.
Yes ... I have done this. Unfortunately that is how I got into this mess. It had been working, but for some reason after about an hour it would no longer respond to requests. So, I would have to restart. I thought It does work with I even went so far as to remove the minikube binaries, and The command was simply At the |
This concludes that this is a real problem and not related to old crud left behind. |
|
sadly, I have the same issue and not know how to get through this... |
|
@John-cn Sadly, I have not progressed any further 😖 |
|
Same issue using Ubuntu 18.04.1 LTS and kvm2 driver 0.25.2 works fine, 0.29 does not. |
|
Windows 10 WSL. Confirmed 0.25.2 works but 0.29 doesn't on my machine. |
|
Unfortunately, same issue here using Windows 10, VirtualBox driver, Minikube 0.30.0 |
|
Chiming in again - for v0.30 Env - win8.1 x64, virtualbox 5.2.12 Only 0.25.2 works. At this stage I'm ready to give up on Minikube and have stopped recommending minikube to associates :( |
|
I am also seeing this issue. Ubuntu 18.10 64bit |
|
Same here: Ubuntu 18.04, minikube 30, kvm2. I'm going to try regressing to 25.0 and see what happens. No Kube For You! |
|
Also experiencing this issue using Minikube 30, KVM2. |
|
Ubuntu 18.04, minikube version: v0.30.0 with kvm2 has the same problem. |
|
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. |
|
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 Make sure all the .kube and .minikube folders are deleted and the VM is also removed before running this command: |
|
Similarly as @herrberk, all works fine from public networks - I only get the error behind a proxy. |
|
I have the exact same problem as @herrberk and the exact same configuration |
|
Same error as @herrberk - If you find the solution please post here. |
|
I was having the very same issue, running a Mint guest VMware machine on a Win10 host. |
Hi, Thanks for your reply. I tried changing my command to "minikube start --vm-driver="hyperv" --memory=8192 --cpus=4 --hyperv-virtual-switch="My New Switch" --v=7 --alsologtostderr --kubernetes-version=v1.12.0" But I am still stuck on Also, error log - Setting up kubeconfig... I am on my company network. |
|
@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 |
|
Same error on: OS: OSX 10.14.1 Mojave 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=virtualboxLog: 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 |
|
Similar error OS: Ubuntu 18.04 |
|
Same issue here (macOS Sierra 10.12.6): |
|
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! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment: Windows 10 64bit v1709, VirtualBox 5.2.6
Minikube version (use
minikube version): v0.25.0cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): v0.25.1What happened:
I'm running the following command:
minikube start --cpus=2 --memory=4096 --kubernetes-version=v1.9.2 --bootstrapper=kubeadmAnd get this error
What you expected to happen:
A running minikube cluster
How to reproduce it (as minimally and precisely as possible):
minikube start --cpus=2 --memory=4096 --kubernetes-version=v1.9.2 --bootstrapper=kubeadmOutput of
minikube logs(if applicable): logs are emptyAnything else do we need to know:
This was already reported under #2018, but the issue was closed. The problem is still present though (at least on Windows, I did a quick check on Ubuntu 16.04 and it worked fine).
The text was updated successfully, but these errors were encountered: