minikube: Mystery hang during /usr/bin/kubeadm init (with no --extra-config options)
BUG REPORT
Environment:
$ minikube version
minikube version: v0.28.0
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
$ grep DriverName ~/.minikube/machines/minikube/config.json
"DriverName": "virtualbox",
$ grep -i ISO ~/.minikube/machines/minikube/config.json
"Boot2DockerURL": "file:///home/hans/.minikube/cache/iso/minikube-v0.28.0.iso",
$ cat /home/hans/.kube/config
apiVersion: v1
clusters:
- cluster:
certificate-authority: /home/hans/.minikube/ca.crt
server: https://192.168.99.103:8443
name: minikube
contexts:
- context:
cluster: minikube
user: minikube
name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
user:
client-certificate: /home/hans/.minikube/client.crt
client-key: /home/hans/.minikube/client.key
What happened: When running minikube start it hangs at Starting cluster components.... In the console of the minikube VM, I get prompted for minikube login: . I can login with root.
What you expected to happen: minikube is started and configured.
How to reproduce it (as minimally and precisely as possible):
minikube delete
minikube start --logtostderr --loglevel 0
Output of minikube logs (if applicable):
Connecting to cluster...
Setting up kubeconfig...
I0627 11:33:56.307740 24241 config.go:101] Using kubeconfig: /home/hans/.kube/config
Starting cluster components...
I0627 11:33:56.308563 24241 ssh_runner.go:80] Run with output: 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
Anything else do we need to know: Installed minikube with
curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
Installed virtualbox with
sudo apt-get remove --purge virtualbox-5.2
sudo apt-get remove --purge virtualbox
rm -rf ~/.config/VirtualBox
sudo dpkg -i ~/Downloads/virtualbox-5.2_5.2.12-122591\~Ubuntu\~xenial_amd64.deb
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 23 (5 by maintainers)
I got the same issue
I’m also experiencing this on MacOS Sierra with minikube v0.28.2 trying to start a Kubernetes v1.10.0 cluster. I’ve tried with hyperkit as well as virtualbox with the same outcome that @frastel posted above. Process exiting with status 1 after sudo /usr/bin/kubeadm alpha phase addon kube-dns
Same here for Minikube 0.28.2. It happens with both VirtualBox and Hyper-V drivers
Logs aren’t really helpful:
We are also hitting this, it looks the same as we were hitting previously as well but the issue was closed - https://github.com/kubernetes/minikube/issues/2765
For now some of us are using 0.25.2 OK. Others have problem with that version which need a newer docker version to pick up a fix so are completely blocked as all newer versions hit this problem
@Arnavion No, I remember it was 1.10.0 and I also tried with 1.9.4 but still fails. I didn’t know there is 1.11.0.
minikube v0.33.1 should now remove mystery hangs. You can watch the output streamed from kubeadm by using --alsologtostderr -v=1.
We’ll also be dividing up the pull & run sections in the UI shortly, which should help, so I’m not closing this issue as obsolete just yet.
Same issue here with: MasOS: 10.14.1 minikube: 0.30.0 VM Driver: virtualbox
After some google, and then try to install driver hyperkit by the instruction here
Homebrew also has a formulae here, I believe it also works fine to install the driver.
And for convenient, set the default driver to hyperkit by
minikube config set vm-driver hyperkit.Finally this issue has gone with minikube: 0.30.0, vm-driver: hyperkit