minikube: Cannot access minikube dashboard
Is this a BUG REPORT or FEATURE REQUEST? : BUG REPORT
Minikube version : v0.20.0
Environment:
- OS (e.g. from /etc/os-release): Ubuntu 12.04.5 LTS
- VM Driver (e.g.
cat ~/.minikube/machines/minikube/config.json | grep DriverName): “DriverName”: “virtualbox” - ISO version (e.g.
cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): “Boot2DockerURL”: “file:///home/nszig/.minikube/cache/iso/minikube-v0.20.0.iso” - Install tools:
- Others:
What happened: I have installed minikube and kubectl on Ubuntu. However i cannot access the dashboard both through the CLI and through the GUI. http://127.0.0.1:8001/ui give the below error { “kind”: “Status”, “apiVersion”: “v1”, “metadata”: {}, “status”: “Failure”, “message”: “no endpoints available for service "kubernetes-dashboard"”, “reason”: “ServiceUnavailable”, “code”: 503 }
And minikube dashboard on the CLI does not open the dashboard
What you expected to happen: I should be able to view the kubernetes dashboard
How to reproduce it (as minimally and precisely as possible): Try the below on Ubuntu 12.04LTS
-
curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.20.0/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
-
curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl
-
chmod +x ./kubectl
-
sudo mv ./kubectl /usr/local/bin/kubectl
-
minikube dashboard
Output: Waiting, endpoint for service is not ready yet… Waiting, endpoint for service is not ready yet… Waiting, endpoint for service is not ready yet… Waiting, endpoint for service is not ready yet… … Could not find finalized endpoint being pointed to by kubernetes-dashboard: Temporary Error: Endpoint for service is not ready yet Temporary Error: Endpoint for service is not ready yet Temporary Error: Endpoint for service is not ready yet Temporary Error: Endpoint for service is not ready yet
http://127.0.0.1:8001/ui { “kind”: “Status”, “apiVersion”: “v1”, “metadata”: {}, “status”: “Failure”, “message”: “no endpoints available for service "kubernetes-dashboard"”, “reason”: “ServiceUnavailable”, “code”: 503 }
Anything else do we need to know: kubectl version: Client Version: version.Info{Major:“1”, Minor:“7”, GitVersion:“v1.7.0”, GitCommit:“d3ada0119e776222f11ec7945e6d860061339aad”, GitTreeState:“clean”, BuildDate:“2017-06-29T23:15:59Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“6”, GitVersion:“v1.6.4”, GitCommit:“d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae”, GitTreeState:“dirty”, BuildDate:“2017-06-22T04:31:09Z”, GoVersion:“go1.7.5”, Compiler:“gc”, Platform:“linux/amd64”}
minikube logs also reports the errors below: … Jul 10 08:46:12 minikube localkube[3237]: I0710 08:46:12.901880 3237 kuberuntime_manager.go:458] Container {Name:php-redis Image:gcr.io/google-samples/gb-frontend:v4 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:80 Protocol:TCP HostIP:}] EnvFrom:[] Env:[{Name:GET_HOSTS_FROM Value:dns ValueFrom:nil}] Resources:{Limits:map[] Requests:map[cpu:{i:{value:100 scale:-3} d:{Dec:<nil>} s:100m Format:DecimalSI} memory:{i:{value:104857600 scale:0} d:{Dec:<nil>} s:100Mi Format:BinarySI}]} VolumeMounts:[{Name:default-token-gqtvf ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it. Jul 10 08:46:14 minikube localkube[3237]: E0710 08:46:14.139555 3237 remote_runtime.go:86] RunPodSandbox from runtime service failed: rpc error: code = 2 desc = unable to pull sandbox image “gcr.io/google_containers/pause-amd64:3.0”: Error response from daemon: Get https://gcr.io/v1/_ping: x509: certificate signed by unknown authority …
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 6
- Comments: 35 (2 by maintainers)
minikube deletefollowed byminikube start --vm-driver hypervalso worked for me under Win 10 Pro.fixed it by deleting cluster, and deleting minikube completely and and reinstalling to 0.28.2 through brew (on mac)
Are you behind a proxy? It looks like the VM isn’t able to reach out to the internet and pull the images. If so, make sure you set the HTTP_PROXY or HTTPS_PROXY variables in
minikube start --docker-env