Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Please provide the following details:
Environment:
Minikube version (use minikube version):
minikube version: v0.28.2
cat ~/.minikube/machines/minikube/config.json | grep DriverName):cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):What happened:
minikube doesn't successfully start / hangs
What you expected to happen:
Minikube starts
How to reproduce it (as minimally and precisely as possible):
I've tried basically every variation:
minikube start -vm-driver hyperkit
minikube start --vm-driver hyperkit --bootstrapper=localkube
minikube start --vm-driver xhyve
minikube start --vm-driver xhyve --bootstrapper=localkube
minikube start --vm-driver virtualbox
minikube start --vm-driver virtualbox --bootstrapper=localkube
Output of minikube logs (if applicable):
see attachment
minikube-logs.zip
Anything else do we need to know:
when using localkube it tries to pull k8s.gcr.io/pause-amd64:3.1, which cannot work:
kubernetes/kubeadm#962
(check journalctl-localkube.log in the zip)
I have stopped, deleted the minikube VM and also deleted ~/.minikube and ~/.kube between runs.
I've only attached log files from hyperkit, the same issues pop up when using the other drivers.
downgrading to 0.25.2 also doesnt help because of the localkube issue.
Is there any way to get minikube running on macOs??
I give up.
so, turns out that dnsmasq will f* everything up for localkube
sudo brew services stop dnsmasq
brew uninstall dnsmasq
at least I can now start minikube with --bootstrapper=localkube
https://github.com/kubernetes/minikube/issues/2456#issuecomment-404403593
I have the same issue with Windows 7 and VirtualBox
On OSX i found that running dnsmasq and setting the listen-address=192.168.64.1 worked for me. The problem seemed an issue with network traffic not being able to get out and reach the internet to pull the docker images.
This appears to be a dupe of #2456 - please re-open if that is not the case.