minikube: Dashboard does not work

In my case taking a coffee worked. Kubernetes need some time to get the pods ready (you can check it with kubectl get pods --all-namespaces). Depending on your internet connection it can take a bit longer (I needed about 7 minutes)

at beginning:

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY     STATUS              RESTARTS   AGE
kube-system   kube-addon-manager-minikube   0/1       ContainerCreating   0          3m

after 3 min:

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY     STATUS              RESTARTS   AGE
kube-system   kube-addon-manager-minikube   1/1       Running             0          4m
kube-system   kube-dns-910330662-xbt1b      0/3       ContainerCreating   0          17s
kube-system   kubernetes-dashboard-c5x10    0/1       ContainerCreating   0          17s

after 7 min:

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY     STATUS              RESTARTS   AGE
kube-system   kube-addon-manager-minikube   1/1       Running             0          6m
kube-system   kube-dns-910330662-xbt1b      0/3       ContainerCreating   0          2m
kube-system   kubernetes-dashboard-c5x10    1/1       Running             0          2m

I had a DNS issue in xhyve. To fix the issue, I ran in minikube ssh:

sudo su
$ echo nameserver 8.8.8.8 > /etc/resolv.conf

The dashboard is just not installed when you initialize minikube for the first time. After you follow the instructions in the dashboard repo it works just fine.

This isn’t true. The dashboard sometimes can take some time to start up, which is what I think we’re seeing here.

@samuelchen That status indicates that the addon-manager is starting up. The addon-manager is responsible for deploying the dashboard, and sometimes this can take a little time to pull and start in addition to the dashboard starting up.

@hayesgm same problem here. I had to change /etc/systemd/resolved.conf (change #DNS line to DNS=8.8.8.8) and restart systemd-resolved service ($ systemctl restart systemd-resolved)

I meet the same problem.

$ kubectl get po --all-namespaces
NAMESPACE     NAME                                    READY     STATUS             RESTARTS   AGE
kube-system   etcd-minikube                           1/1       Running            0          2m
kube-system   kube-addon-manager-minikube             1/1       Running            4          2h
kube-system   kube-apiserver-minikube                 1/1       Running            0          2m
kube-system   kube-controller-manager-minikube        1/1       Running            0          2m
kube-system   kube-dns-86f4d74b45-x2gn8               3/3       Running            8          2h
kube-system   kube-proxy-62mwx                        1/1       Running            0          1m
kube-system   kube-scheduler-minikube                 1/1       Running            0          2m
kube-system   kubernetes-dashboard-5498ccf677-fh2rj   0/1       CrashLoopBackOff   11         2h
kube-system   storage-provisioner                     1/1       Running            4          2h

The solution is:

$ minikube stop
$ minikube delete
$ minikube start

@galvesribeiro you can use minikube logs to check logs. I met the same issue as proxy config is required for docker. Check more on https://stackoverflow.com/questions/23111631/cannot-download-docker-images-behind-a-proxy After that, I can start the addon manage success

Same problem here… 8hs and nothing happen… Is there a way to see logs to try understand what is happening?

Thanks! Appreciate any help.

When I start with 1.7.4 version flag. All pods empty: yangyaos-iMac:deployment yangyao$ k8allpods No resources found.

When I start with 1.7.0 default, then everything is working. Is anyone else encountering this behaviour?

Starting local Kubernetes v1.7.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Starting cluster components...
Connecting to cluster...
Setting up kubeconfig...
Kubectl is now configured to use the cluster.
yangyaos-iMac:deployment yangyao$ k8allpods
NAMESPACE     NAME                           READY     STATUS              RESTARTS   AGE
default       greeter-srv-2395100891-pkch2   0/1       ErrImageNeverPull   0          48m
kube-system   kube-addon-manager-minikube    1/1       Running             3          23h
kube-system   kube-dns-910330662-zp5ks       3/3       Running             9          23h
kube-system   kubernetes-dashboard-sh55m     1/1       Running             4          23h

@zedalaye’s solution worked for me coupled with minikube stop and minikube start.