Minikube: Hung after "successfully loaded all cached images" (dnsmasq conflict)

[tyranron]

Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.24.1

• OS (e.g. from /etc/os-release): macOS 10.12.6 (Darwin 16.7.0)
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): hyperkit
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): minikube-v0.23.6.iso
• Install tools: brew
• Others: kubeadm bootstrapper, 1.9.2 Kubernetes version

What happened:
Starting Minikube with the following command hangs indefinitely.

minikube start --vm-driver=hyperkit --bootstrapper=kubeadm --kubernetes-version=v1.9.2 \
               --disk-size=10g --loglevel=0 --logtostderr

What you expected to happen:
Successfully started Minikube.

Output of minikube logs (if applicable):

W0124 15:54:45.635739   97574 root.go:148] Error reading config file at /Users/d/.minikube/config/config.json: open /Users/d/.minikube/config/config.json: no such file or directory
I0124 15:54:45.635932   97574 notify.go:109] Checking for updates...
I0124 15:54:45.994487   97574 cache_images.go:290] Attempting to cache image: gcr.io/k8s-minikube/storage-provisioner:v1.8.0 at /Users/d/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.0
I0124 15:54:45.994520   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/pause-amd64:3.0 at /Users/d/.minikube/cache/images/gcr.io/google_containers/pause-amd64_3.0
I0124 15:54:45.994544   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.4 at /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-kube-dns-amd64_1.14.4
I0124 15:54:45.994572   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.4 at /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0124 15:54:45.994574   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/kubernetes-dashboard-amd64:v1.6.3 at /Users/d/.minikube/cache/images/gcr.io/google_containers/kubernetes-dashboard-amd64_v1.6.3
I0124 15:54:45.994613   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/etcd-amd64:3.0.17 at /Users/d/.minikube/cache/images/gcr.io/google_containers/etcd-amd64_3.0.17
I0124 15:54:45.994595   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.4 at /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-sidecar-amd64_1.14.4
I0124 15:54:45.994640   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/kube-proxy-amd64:v1.9.2 at /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-proxy-amd64_v1.9.2
I0124 15:54:45.994645   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/kube-controller-manager-amd64:v1.9.2 at /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-controller-manager-amd64_v1.9.2
I0124 15:54:45.994671   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/kube-scheduler-amd64:v1.9.2 at /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-scheduler-amd64_v1.9.2
Starting local Kubernetes v1.9.2 cluster...
Starting VM...
I0124 15:54:45.994681   97574 cache_images.go:290] Attempting to cache image: gcr.io/google_containers/kube-apiserver-amd64:v1.9.2 at /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-apiserver-amd64_v1.9.2
I0124 15:54:45.994489   97574 cache_images.go:290] Attempting to cache image: gcr.io/google-containers/kube-addon-manager:v6.4-beta.2 at /Users/d/.minikube/cache/images/gcr.io/google-containers/kube-addon-manager_v6.4-beta.2
I0124 15:54:45.995320   97574 cache_images.go:78] Successfully cached all images.
I0124 15:54:45.995337   97574 cluster.go:70] Machine does not exist... provisioning new machine
I0124 15:54:45.995346   97574 cluster.go:71] Provisioning machine with config: {MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v0.23.6.iso Memory:2048 CPUs:2 DiskSize:10000 VMDriver:hyperkit XhyveDiskDriver:ahci-hd DockerEnv:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.99.1/24 HypervVirtualSwitch: KvmNetwork:default Downloader:{} DockerOpt:[] DisableDriverMounts:false}
I0124 15:54:45.995705   97574 downloader.go:56] Not caching ISO, using https://storage.googleapis.com/minikube/iso/minikube-v0.23.6.iso
I0124 15:55:29.923554   97574 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server.pem
I0124 15:55:29.933793   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
I0124 15:55:29.945192   97574 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server-key.pem
I0124 15:55:29.950820   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
I0124 15:55:29.961994   97574 ssh_runner.go:57] Run: sudo rm -f /etc/docker/ca.pem
I0124 15:55:29.967599   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
Getting VM IP address...
Moving files into cluster...
I0124 15:55:32.442714   97574 kubeadm.go:194] Container runtime flag provided with no value, using defaults.
I0124 15:55:32.443019   97574 ssh_runner.go:57] Run: sudo rm -f /usr/bin/kubeadm
I0124 15:55:32.443227   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.0
I0124 15:55:32.443309   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/storage-provisioner_v1.8.0
I0124 15:55:32.443319   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0124 15:55:32.443412   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0124 15:55:32.443661   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-sidecar-amd64_1.14.4
I0124 15:55:32.443807   97574 ssh_runner.go:57] Run: sudo rm -f /usr/bin/kubelet
I0124 15:55:32.443855   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/etcd-amd64_3.0.17
I0124 15:55:32.443808   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/k8s-dns-sidecar-amd64_1.14.4
I0124 15:55:32.444214   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/kubernetes-dashboard-amd64_v1.6.3
I0124 15:55:32.444298   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/kubernetes-dashboard-amd64_v1.6.3
I0124 15:55:32.444462   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google-containers/kube-addon-manager_v6.4-beta.2
I0124 15:55:32.444545   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-addon-manager_v6.4-beta.2
I0124 15:55:32.444697   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/pause-amd64_3.0
I0124 15:55:32.444771   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/pause-amd64_3.0
I0124 15:55:32.444865   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-kube-dns-amd64_1.14.4
I0124 15:55:32.444904   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/etcd-amd64_3.0.17
I0124 15:55:32.444915   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/k8s-dns-kube-dns-amd64_1.14.4
I0124 15:55:32.444971   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-scheduler-amd64_v1.9.2
I0124 15:55:32.446533   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-scheduler-amd64_v1.9.2
I0124 15:55:32.445031   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-proxy-amd64_v1.9.2
I0124 15:55:32.446997   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-proxy-amd64_v1.9.2
I0124 15:55:32.445055   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-controller-manager-amd64_v1.9.2
I0124 15:55:32.447449   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-controller-manager-amd64_v1.9.2
I0124 15:55:32.445062   97574 cache_images.go:193] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-apiserver-amd64_v1.9.2
I0124 15:55:32.447670   97574 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-apiserver-amd64_v1.9.2
I0124 15:55:32.472165   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.478361   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.479122   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.483901   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.484047   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.486135   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.486195   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.486236   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.486266   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.490086   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.492396   97574 ssh_runner.go:57] Run: sudo mkdir -p /usr/bin
I0124 15:55:32.493912   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.495803   97574 ssh_runner.go:57] Run: sudo mkdir -p /usr/bin
I0124 15:55:32.499931   97574 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0124 15:55:32.740479   97574 ssh_runner.go:57] Run: docker load -i /tmp/pause-amd64_3.0
I0124 15:55:33.571180   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/pause-amd64_3.0
I0124 15:55:33.704964   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/pause-amd64_3.0 from cache
I0124 15:55:35.820636   97574 ssh_runner.go:57] Run: docker load -i /tmp/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0124 15:55:35.826334   97574 ssh_runner.go:57] Run: docker load -i /tmp/k8s-dns-sidecar-amd64_1.14.4
I0124 15:55:36.544930   97574 ssh_runner.go:57] Run: docker load -i /tmp/k8s-dns-kube-dns-amd64_1.14.4
I0124 15:55:37.224508   97574 ssh_runner.go:57] Run: docker load -i /tmp/kube-scheduler-amd64_v1.9.2
I0124 15:55:38.890358   97574 ssh_runner.go:57] Run: docker load -i /tmp/kube-addon-manager_v6.4-beta.2
I0124 15:55:39.183764   97574 ssh_runner.go:57] Run: docker load -i /tmp/storage-provisioner_v1.8.0
I0124 15:55:40.328622   97574 ssh_runner.go:57] Run: docker load -i /tmp/kube-controller-manager-amd64_v1.9.2
I0124 15:55:41.094479   97574 ssh_runner.go:57] Run: docker load -i /tmp/kube-apiserver-amd64_v1.9.2
I0124 15:55:41.590816   97574 ssh_runner.go:57] Run: docker load -i /tmp/kube-proxy-amd64_v1.9.2
I0124 15:55:42.286626   97574 ssh_runner.go:57] Run: docker load -i /tmp/kubernetes-dashboard-amd64_v1.6.3
I0124 15:55:43.508220   97574 ssh_runner.go:57] Run: docker load -i /tmp/etcd-amd64_3.0.17
I0124 15:55:50.541385   97574 ssh_runner.go:57] Run: sudo rm -f /lib/systemd/system/kubelet.service
I0124 15:55:50.550658   97574 ssh_runner.go:57] Run: sudo mkdir -p /lib/systemd/system
I0124 15:55:50.579264   97574 ssh_runner.go:57] Run: sudo rm -f /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
I0124 15:55:50.601668   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/systemd/system/kubelet.service.d
I0124 15:55:50.637225   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/kubeadm.yaml
I0124 15:55:50.655099   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib
I0124 15:55:50.693007   97574 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/storageclass.yaml
I0124 15:55:50.706238   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0124 15:55:50.734091   97574 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/manifests/addon-manager.yaml
I0124 15:55:50.757366   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/manifests/
I0124 15:55:50.784174   97574 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/storage-provisioner.yaml
I0124 15:55:50.796247   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0124 15:55:50.842683   97574 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/dashboard-rc.yaml
I0124 15:55:50.857833   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0124 15:55:50.928570   97574 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/dashboard-svc.yaml
I0124 15:55:50.938379   97574 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0124 15:55:50.975066   97574 ssh_runner.go:57] Run: 
sudo systemctl daemon-reload &&
sudo systemctl enable kubelet &&
sudo systemctl start kubelet

Setting up certs...
I0124 15:55:51.588520   97574 certs.go:46] Setting up certificates for IP: 192.168.64.7
I0124 15:55:51.618158   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/ca.crt
I0124 15:55:51.699274   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:51.780502   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/ca.key
I0124 15:55:51.798756   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:51.929882   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/apiserver.crt
I0124 15:55:51.962648   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:52.019281   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/apiserver.key
I0124 15:55:52.031919   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:52.064108   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client-ca.crt
I0124 15:55:52.072806   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:52.116382   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client-ca.key
I0124 15:55:52.131199   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:52.179459   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client.crt
I0124 15:55:52.197880   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:52.237333   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client.key
I0124 15:55:52.269818   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0124 15:55:52.341926   97574 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/kubeconfig
I0124 15:55:52.357115   97574 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube
Connecting to cluster...
Setting up kubeconfig...
I0124 15:55:52.393241   97574 config.go:101] Using kubeconfig:  /Users/d/.kube/config
Starting cluster components...
I0124 15:55:52.396151   97574 ssh_runner.go:57] Run: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks
I0124 15:55:58.187604   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/k8s-dns-sidecar-amd64_1.14.4
I0124 15:55:58.205918   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-sidecar-amd64_1.14.4 from cache
I0124 15:55:59.144306   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0124 15:55:59.179953   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64_1.14.4 from cache
I0124 15:56:01.313204   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/k8s-dns-kube-dns-amd64_1.14.4
I0124 15:56:01.368906   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/k8s-dns-kube-dns-amd64_1.14.4 from cache
I0124 15:56:02.683674   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-scheduler-amd64_v1.9.2
I0124 15:56:02.697085   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-scheduler-amd64_v1.9.2 from cache
I0124 15:56:04.802094   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/storage-provisioner_v1.8.0
I0124 15:56:04.815293   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.0 from cache
I0124 15:56:07.123482   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-addon-manager_v6.4-beta.2
I0124 15:56:07.138879   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google-containers/kube-addon-manager_v6.4-beta.2 from cache
I0124 15:56:09.008966   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-controller-manager-amd64_v1.9.2
I0124 15:56:09.024160   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-controller-manager-amd64_v1.9.2 from cache
I0124 15:56:09.496298   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/kubernetes-dashboard-amd64_v1.6.3
I0124 15:56:09.514005   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/kubernetes-dashboard-amd64_v1.6.3 from cache
I0124 15:56:11.474098   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-proxy-amd64_v1.9.2
I0124 15:56:11.493899   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-proxy-amd64_v1.9.2 from cache
I0124 15:56:11.913717   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-apiserver-amd64_v1.9.2
I0124 15:56:11.927983   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/kube-apiserver-amd64_v1.9.2 from cache
I0124 15:56:12.561623   97574 ssh_runner.go:57] Run: sudo rm -rf /tmp/etcd-amd64_3.0.17
I0124 15:56:12.575397   97574 cache_images.go:219] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google_containers/etcd-amd64_3.0.17 from cache
I0124 15:56:12.575470   97574 cache_images.go:98] Successfully loaded all cached images.
^C

Anything else do we need to know:
kubectl delete does not help.

Always hangs after cache_images.go:98] Successfully loaded all cached images. line.

[r2d4]

You'll need to wait for #2458, which is compatible with >= 1.9.0

[tyranron]

@r2d4 still facing this issue after upgrade 😕

Environment:

Minikube version (use minikube version): v0.25.0

• OS: macOS 10.12.6 (Darwin 16.7.0)
• VM Driver: hyperkit
• ISO version: minikube-v0.25.1.iso
• Install tools: brew
• Others: kubeadm bootstrapper, 1.9.2 Kubernetes version

Output of minikube logs (if applicable):

+ minikube start --bootstrapper=kubeadm --kubernetes-version=v1.9.2 --vm-driver=hyperkit --disk-size=10g --loglevel=0 --logtostderr
I0127 11:34:46.123517     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/k8s-dns-kube-dns-amd64:1.14.4 at /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-kube-dns-amd64_1.14.4
I0127 11:34:46.123557     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64:1.14.4 at /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0127 11:34:46.123567     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/kube-proxy-amd64:v1.9.2 at /Users/d/.minikube/cache/images/k8s.gcr.io/kube-proxy-amd64_v1.9.2
I0127 11:34:46.123583     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/pause-amd64:3.0 at /Users/d/.minikube/cache/images/k8s.gcr.io/pause-amd64_3.0
I0127 11:34:46.123589     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/kube-scheduler-amd64:v1.9.2 at /Users/d/.minikube/cache/images/k8s.gcr.io/kube-scheduler-amd64_v1.9.2
I0127 11:34:46.123517     384 cache_images.go:292] Attempting to cache image: gcr.io/google-containers/kube-addon-manager:v6.5 at /Users/d/.minikube/cache/images/gcr.io/google-containers/kube-addon-manager_v6.5
I0127 11:34:46.123530     384 cache_images.go:292] Attempting to cache image: gcr.io/k8s-minikube/storage-provisioner:v1.8.0 at /Users/d/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.0
Starting local Kubernetes v1.9.2 cluster...
I0127 11:34:46.123549     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1 at /Users/d/.minikube/cache/images/k8s.gcr.io/kubernetes-dashboard-amd64_v1.8.1
Starting VM...
I0127 11:34:46.123600     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/k8s-dns-sidecar-amd64:1.14.4 at /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-sidecar-amd64_1.14.4
I0127 11:34:46.123612     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/kube-controller-manager-amd64:v1.9.2 at /Users/d/.minikube/cache/images/k8s.gcr.io/kube-controller-manager-amd64_v1.9.2
I0127 11:34:46.123620     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/etcd-amd64:3.0.17 at /Users/d/.minikube/cache/images/k8s.gcr.io/etcd-amd64_3.0.17
I0127 11:34:46.123623     384 cache_images.go:292] Attempting to cache image: k8s.gcr.io/kube-apiserver-amd64:v1.9.2 at /Users/d/.minikube/cache/images/k8s.gcr.io/kube-apiserver-amd64_v1.9.2
I0127 11:34:46.124196     384 cache_images.go:79] Successfully cached all images.
I0127 11:34:46.123737     384 cluster.go:70] Machine does not exist... provisioning new machine
I0127 11:34:46.124220     384 cluster.go:71] Provisioning machine with config: {MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v0.25.1.iso Memory:2048 CPUs:2 DiskSize:10000 VMDriver:hyperkit XhyveDiskDriver:ahci-hd DockerEnv:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.99.1/24 HypervVirtualSwitch: KvmNetwork:default Downloader:{} DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID:}
I0127 11:34:46.124780     384 downloader.go:56] Not caching ISO, using https://storage.googleapis.com/minikube/iso/minikube-v0.25.1.iso
I0127 11:35:25.597709     384 ssh_runner.go:57] Run: sudo rm -f /etc/docker/ca.pem
I0127 11:35:25.608350     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
I0127 11:35:25.627189     384 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server.pem
I0127 11:35:25.633624     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
I0127 11:35:25.647601     384 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server-key.pem
I0127 11:35:25.656364     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
Getting VM IP address...
Moving files into cluster...
I0127 11:35:27.910891     384 kubeadm.go:194] Container runtime flag provided with no value, using defaults.
I0127 11:35:27.910911     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/kubernetes-dashboard-amd64_v1.8.1
I0127 11:35:27.910953     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/google-containers/kube-addon-manager_v6.5
I0127 11:35:27.911031     384 ssh_runner.go:57] Run: sudo rm -f /tmp/kubernetes-dashboard-amd64_v1.8.1
I0127 11:35:27.911054     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/pause-amd64_3.0
I0127 11:35:27.911097     384 ssh_runner.go:57] Run: sudo rm -f /tmp/pause-amd64_3.0
I0127 11:35:27.911106     384 ssh_runner.go:57] Run: sudo rm -f /usr/bin/kubeadm
I0127 11:35:27.910912     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.0
I0127 11:35:27.911165     384 ssh_runner.go:57] Run: sudo rm -f /usr/bin/kubelet
I0127 11:35:27.911167     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-kube-dns-amd64_1.14.4
I0127 11:35:27.911202     384 ssh_runner.go:57] Run: sudo rm -f /tmp/storage-provisioner_v1.8.0
I0127 11:35:27.911216     384 ssh_runner.go:57] Run: sudo rm -f /tmp/k8s-dns-kube-dns-amd64_1.14.4
I0127 11:35:27.911230     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/kube-proxy-amd64_v1.9.2
I0127 11:35:27.911218     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/etcd-amd64_3.0.17
I0127 11:35:27.911203     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-sidecar-amd64_1.14.4
I0127 11:35:27.911031     384 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-addon-manager_v6.5
I0127 11:35:27.911617     384 ssh_runner.go:57] Run: sudo rm -f /tmp/k8s-dns-sidecar-amd64_1.14.4
I0127 11:35:27.911268     384 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-proxy-amd64_v1.9.2
I0127 11:35:27.911272     384 ssh_runner.go:57] Run: sudo rm -f /tmp/etcd-amd64_3.0.17
I0127 11:35:27.911181     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0127 11:35:27.911809     384 ssh_runner.go:57] Run: sudo rm -f /tmp/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0127 11:35:27.911280     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/kube-scheduler-amd64_v1.9.2
I0127 11:35:27.911905     384 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-scheduler-amd64_v1.9.2
I0127 11:35:27.911285     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/kube-controller-manager-amd64_v1.9.2
I0127 11:35:27.911301     384 cache_images.go:194] Loading image from cache at  /Users/d/.minikube/cache/images/k8s.gcr.io/kube-apiserver-amd64_v1.9.2
I0127 11:35:27.912003     384 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-controller-manager-amd64_v1.9.2
I0127 11:35:27.912046     384 ssh_runner.go:57] Run: sudo rm -f /tmp/kube-apiserver-amd64_v1.9.2
I0127 11:35:27.942413     384 ssh_runner.go:57] Run: sudo mkdir -p /usr/bin
I0127 11:35:27.945581     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.955220     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.955227     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.983006     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.985039     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.988447     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.988468     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.989880     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.990123     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:27.996500     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:28.006001     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:28.006060     384 ssh_runner.go:57] Run: sudo mkdir -p /usr/bin
I0127 11:35:28.006060     384 ssh_runner.go:57] Run: sudo mkdir -p /tmp
I0127 11:35:28.451024     384 ssh_runner.go:57] Run: docker load -i /tmp/pause-amd64_3.0
I0127 11:35:29.692483     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/pause-amd64_3.0
I0127 11:35:29.893014     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/pause-amd64_3.0 from cache
I0127 11:35:31.857584     384 ssh_runner.go:57] Run: docker load -i /tmp/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0127 11:35:32.085599     384 ssh_runner.go:57] Run: docker load -i /tmp/k8s-dns-sidecar-amd64_1.14.4
I0127 11:35:32.474202     384 ssh_runner.go:57] Run: docker load -i /tmp/k8s-dns-kube-dns-amd64_1.14.4
I0127 11:35:32.791104     384 ssh_runner.go:57] Run: docker load -i /tmp/kube-scheduler-amd64_v1.9.2
I0127 11:35:34.566722     384 ssh_runner.go:57] Run: docker load -i /tmp/kube-addon-manager_v6.5
I0127 11:35:34.673726     384 ssh_runner.go:57] Run: docker load -i /tmp/storage-provisioner_v1.8.0
I0127 11:35:36.376734     384 ssh_runner.go:57] Run: docker load -i /tmp/kube-controller-manager-amd64_v1.9.2
I0127 11:35:36.958006     384 ssh_runner.go:57] Run: docker load -i /tmp/kube-apiserver-amd64_v1.9.2
I0127 11:35:37.026166     384 ssh_runner.go:57] Run: docker load -i /tmp/kube-proxy-amd64_v1.9.2
I0127 11:35:37.893142     384 ssh_runner.go:57] Run: docker load -i /tmp/kubernetes-dashboard-amd64_v1.8.1
I0127 11:35:38.531940     384 ssh_runner.go:57] Run: docker load -i /tmp/etcd-amd64_3.0.17
I0127 11:35:47.770881     384 ssh_runner.go:57] Run: sudo rm -f /lib/systemd/system/kubelet.service
I0127 11:35:47.800421     384 ssh_runner.go:57] Run: sudo mkdir -p /lib/systemd/system
I0127 11:35:47.854940     384 ssh_runner.go:57] Run: sudo rm -f /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
I0127 11:35:47.898698     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/systemd/system/kubelet.service.d
I0127 11:35:47.944013     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/kubeadm.yaml
I0127 11:35:47.962633     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib
I0127 11:35:48.031456     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/manifests/addon-manager.yaml
I0127 11:35:48.062648     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/manifests/
I0127 11:35:48.114056     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/dashboard-dp.yaml
I0127 11:35:48.128511     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0127 11:35:48.149159     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/dashboard-svc.yaml
I0127 11:35:48.162699     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0127 11:35:48.196916     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/storage-provisioner.yaml
I0127 11:35:48.208074     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0127 11:35:48.236709     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/ingress-configmap.yaml
I0127 11:35:48.249461     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0127 11:35:48.277736     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/ingress-rc.yaml
I0127 11:35:48.291672     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0127 11:35:48.337285     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/ingress-svc.yaml
I0127 11:35:48.353212     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0127 11:35:48.388626     384 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/storageclass.yaml
I0127 11:35:48.399405     384 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I0127 11:35:48.419793     384 ssh_runner.go:57] Run: 
sudo systemctl daemon-reload &&
sudo systemctl enable kubelet &&
sudo systemctl start kubelet

Setting up certs...
I0127 11:35:48.669595     384 certs.go:46] Setting up certificates for IP: 192.168.64.10
I0127 11:35:48.707284     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/ca.crt
I0127 11:35:48.725027     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:48.750784     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/ca.key
I0127 11:35:48.771197     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:48.832224     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/apiserver.crt
I0127 11:35:48.849508     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:48.911393     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/apiserver.key
I0127 11:35:48.923460     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:48.965217     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client-ca.crt
I0127 11:35:48.979112     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:49.024973     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client-ca.key
I0127 11:35:49.038594     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:49.068186     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client.crt
I0127 11:35:49.082840     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:49.115936     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/certs/proxy-client.key
I0127 11:35:49.132327     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube/certs/
I0127 11:35:49.170858     384 ssh_runner.go:57] Run: sudo rm -f /var/lib/localkube/kubeconfig
I0127 11:35:49.184219     384 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/localkube
Connecting to cluster...
Setting up kubeconfig...
I0127 11:35:49.222103     384 config.go:101] Using kubeconfig:  /Users/d/.kube/config
Starting cluster components...
I0127 11:35:49.225296     384 ssh_runner.go:57] Run: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --skip-preflight-checks
I0127 11:35:57.108062     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/k8s-dns-sidecar-amd64_1.14.4
I0127 11:35:57.119079     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-sidecar-amd64_1.14.4 from cache
I0127 11:35:57.125637     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/k8s-dns-dnsmasq-nanny-amd64_1.14.4
I0127 11:35:57.135078     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64_1.14.4 from cache
I0127 11:35:59.069552     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/k8s-dns-kube-dns-amd64_1.14.4
I0127 11:35:59.085489     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/k8s-dns-kube-dns-amd64_1.14.4 from cache
I0127 11:36:00.464455     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-scheduler-amd64_v1.9.2
I0127 11:36:00.476290     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/kube-scheduler-amd64_v1.9.2 from cache
I0127 11:36:03.216038     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/storage-provisioner_v1.8.0
I0127 11:36:03.225723     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.0 from cache
I0127 11:36:05.555590     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-addon-manager_v6.5
I0127 11:36:05.566917     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/gcr.io/google-containers/kube-addon-manager_v6.5 from cache
I0127 11:36:07.678697     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-controller-manager-amd64_v1.9.2
I0127 11:36:07.689279     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/kubernetes-dashboard-amd64_v1.8.1
I0127 11:36:07.710883     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/kube-controller-manager-amd64_v1.9.2 from cache
I0127 11:36:07.726511     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/kubernetes-dashboard-amd64_v1.8.1 from cache
I0127 11:36:08.336436     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-proxy-amd64_v1.9.2
I0127 11:36:08.351626     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/kube-proxy-amd64_v1.9.2 from cache
I0127 11:36:09.268690     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/kube-apiserver-amd64_v1.9.2
I0127 11:36:09.286318     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/kube-apiserver-amd64_v1.9.2 from cache
I0127 11:36:09.621168     384 ssh_runner.go:57] Run: sudo rm -rf /tmp/etcd-amd64_3.0.17
I0127 11:36:09.633227     384 cache_images.go:220] Successfully loaded image /Users/d/.minikube/cache/images/k8s.gcr.io/etcd-amd64_3.0.17 from cache
I0127 11:36:09.633346     384 cache_images.go:99] Successfully loaded all cached images.
^C

[apolloFER]

Had the exact same issue with the exact same logs. Turns out that all went to hell because I installed dnsmasq and it was running on port 53 of my host (and probably overriding minikube's DNS server or something). Therefor the minikube VM didn't receive any DNS replies (since the host is set as the dns nameserver for the VM). You might check that.

[tyranron]

Btw, I also have dnsmasq installed and running.

[apolloFER]

Is it running on port 53? You're going to have to move it to a different port because this messes up DNS resolution for the guest. I was looking into the guest logs and it can not resolve simple DNS queries such as google etc. It is because minikube sets up it's own DNS some where (probably using Hyperkit) which listens to :53 and provides the DNS nameserver for the guest. I guess the solution (from minikube point of view) would be to bind only on the virtual network interface (192.168.64.1:53) and dnsmasq also should bind only to localhost or something. Because in our use case, dnsmasq is hijacking DNS requests which are meant for minikube's DNS resolver. Or perhaps, minikube should bind its DNS resolver to some other port (because there are probably a lot of people running their own dns resolvers on hosts).

[apolloFER]

And it only becomes obvious if you try to use kubeadm (it hangs with it). But even without it k8s can not start any containers (because it can not pull them). It appears as if minikube has started but nothing works.

[sandakith]

have the same issue, any workaround or suggestions ...

[marcqualie]

Confirmed this also happens due to dnsmasq. Disabling this locally, minikube start works as expected. I changed my config to bind to lo0 only with listen address set to 127.0.0.1 and that still prevents minikube from starting.

EDIT: Updating my dnsmasq config to listen-address=0.0.0.0 got this working. Make sure there's a firewall active to prevent exposing your DNS server to the world.

[einkoro]

Is there any work around for this while only binding to 127.0.0.1?

[kojuka]

after about a week of hassle I finally got minikube working by uninstalling dnsmasq.

brew services stop dnsmasq
brew uninstall dnsmasq
minikube stop
minikube delete
rm -rf ~/.minikube
rm -rf ~/.kube
minikube start --vm-driver=hyperkit

➜  ~ minikube start --vm-driver=hyperkit
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Downloading Minikube ISO
 153.08 MB / 153.08 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubelet v1.10.0
Downloading kubeadm 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...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
➜  ~

[bojleros]

It seems that minikube or hyperkit is messing with 53/udp and/or 53/tcp:

test$ minikube status minikube: Running cluster: Running kubectl: Correctly Configured: pointing to minikube-vm at 192.168.64.20 test$ docker run -d --rm --privileged --name dns --user 0 -p 53:53/udp -p 53:53/tcp andyshinn/dnsmasq:2.75 -d -k -i eth0 -a 0.0.0.0 -A /dev/192.168.64.19 29da17ea3edf7d72bbe674cbc445eb547d2c16e73dce184eedec22415ac9344b docker: Error response from daemon: driver failed programming external connectivity on endpoint dns (4c33f70a495b97ac919741aab5c7168e3be24af82943f353e55bb39512cbfded): Error starting userland proxy: Bind for 0.0.0.0:53: unexpected error (Failure EADDRINUSE). test$ docker run -d --rm --privileged --name dns --user 0 -p 54:53/udp -p 54:53/tcp andyshinn/dnsmasq:2.75 -d -k -i eth0 -a 0.0.0.0 -A /dev/192.168.64.19 25deaa33d3df520c5db272d1695235aa9c811eed799a9dd06af89378b23aed7a test$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 25deaa33d3df andyshinn/dnsmasq:2.75 "dnsmasq -k -d -k -i…" 8 seconds ago Up 6 seconds 0.0.0.0:54->53/tcp, 0.0.0.0:54->53/udp dns test$ docker stop dns dns test$

I cannot determine the process since netstat and lsof are not showing anything on this port. Docker ps -a is empty so it is not another container that locks this two ports.

PS. I have had 'minikube start' freeze (and error couple of minutes later) when i had dns server running on 53 tcp/udp before issuing minikube start.

[vchrisb]

For me it worked to start dnsmasq on a different port and configure mdnsresponder accordingly.
dnsmasq.conf

listen-address=127.0.0.1
port=5354
address=/.minikube.local/192.168.64.11

and /etc/resolver/local

port 5354
nameserver 127.0.0.1

[thecrypticace]

@vchrisb That works flawlessly, thanks!

[maicohjf]

1. Set configuration context $ kubectl config use-context k8s
   Monitor the logs of Pod foobar and
    Extract log lines corresponding to error unable-to-access-website
    Write them to /opt/KULM00201/foobar
   Question weight 5%
   Answer:
   $ kubectl logs pod foobar | grep “ unable-to-access-website ” >
   /opt/KULM00201/foobar

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[tstromberg]

This no longer happens in modern (v1.0+) minikube releases.

[kbakk]

Not sure this issue "no longer happens in modern (v1.0+) minikube releases" - I'm on v1.11.0 and seeing this. I did get a warning though ("This VM is having trouble accessing https://k8s.gcr.io"):

➜ minikube start --memory 6G
😄  minikube v1.11.0 on Darwin 10.15.6
✨  Automatically selected the hyperkit driver
👍  Starting control plane node minikube in cluster minikube
🔥  Creating hyperkit VM (CPUs=2, Memory=6144MB, Disk=20000MB) ...
🎉  minikube 1.12.1 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.12.1
💡  To disable this notice, run: 'minikube config set WantUpdateNotification false'

❗  This VM is having trouble accessing https://k8s.gcr.io
💡  To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube"

Suggestion to set dnsmasq to listen on non-default DNS port worked though.

[jasperf]

/etc/resolver/local

Was this local resolver tweak besides dnsmasq.conf change on a Mac @vchrisb ? Do not have /etc/resolver/local now.. only a test file there.

[vchrisb]

@jasperf I created a small blog on that topic a while ago: https://banck.net/2018/12/using-dnsmasq-on-mac-os-for-local-development/

[jasperf]

@vchrisb Thanks. Checking it out and do have Minikube running now and can keep dnsmaq up and running with Laravel Valet though the services nginx, php and dnsmasq now run as root for some reason. They do work though and Valet and Minikube both work now!