Cant start minikube dashboard #9473
Comments
|
@tokomeno does deleting and starting it again helps ? mind trying this? |
|
/triage needs-information |
k8s-ci-robot
added
triage/needs-information
|
I seem to have similar issue on Ubuntu 20.04.1 LTS with docker driver.
$ minikube version
minikube version: v1.14.0
commit: b09ee50ec047410326a85435f4d99026f9c4f5c4deleting and starting again does not help minikube logs |
|
I discovered that there is kubectl that can be called from minikube and this is what is lists and I can get minikube start
minikube-m02 minikube-m03 Now that the worker nodes are running let me try figure the type Worker shows up in ROLES through kubelet get nodes and it does not for workers, although ready? minikube kubectl get nodes minikube service list Now lest see how it behaves for node add deletes out of sequence to prove that ether delete or sequencing of node name created issues for adding and deleting nodes. $ minikube kubectl get nodes
X Exiting due to MK_USAGE: Usage: minikube node [add|start|stop|delete|list] pramchan@ubuntu131:~$ minikube kubectl get nodes
Since it is pointing to #7538.
|
I have tried it many times but does not helped. $ minikube start $ minikube dashboard --alsologtostderr W1018 19:43:29.932920 871455 out.go:145] ❌ Exiting due to HOST_KUBECTL_PROXY: readByteWithTimeout: EOF W1018 19:43:29.933252 871455 out.go:145] 😿 If the above advice does not help, please let us know: |
|
My bad sorry guys, looks like I was using Kubernetes with microk8s, I have removed it and it works fine. |
How did you remove the microK8s? |
same here, the issue was with k3s , to remove it just make |
yes.i need the same. thanks! |
|
For Windows users change the visualization. for me this worked: |
|
Worked for me after I did |
Steps to reproduce the issue:
Full output of failed command:
~$ minikube start
😄 minikube v1.13.1 on Ubuntu 20.04
✨ Using the docker driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🔥 Creating docker container (CPUs=2, Memory=2200MB) ...
🐳 Preparing Kubernetes v1.19.2 on Docker 19.03.8 ...
🔎 Verifying Kubernetes components...
🌟 Enabled addons: default-storageclass, storage-provisioner
🏄 Done! kubectl is now configured to use "minikube" by default
~$ minikube dashboard --alsologtostderr
I1015 16:49:55.289882 2866294 mustload.go:66] Loading cluster: minikube
I1015 16:49:55.290724 2866294 cli_runner.go:110] Run: docker container inspect minikube --format={{.State.Status}}
I1015 16:49:55.348400 2866294 host.go:65] Checking if "minikube" exists ...
I1015 16:49:55.348710 2866294 api_server.go:146] Checking apiserver status ...
I1015 16:49:55.348775 2866294 ssh_runner.go:148] Run: sudo pgrep -xnf kube-apiserver.minikube.
I1015 16:49:55.348839 2866294 cli_runner.go:110] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "22/tcp") 0).HostPort}}'" minikube
I1015 16:49:55.404381 2866294 sshutil.go:44] new ssh client: &{IP:127.0.0.1 Port:32771 SSHKeyPath:/home/tornike/.minikube/machines/minikube/id_rsa Username:docker}
I1015 16:49:55.637629 2866294 ssh_runner.go:148] Run: sudo egrep ^[0-9]+:freezer: /proc/1597/cgroup
I1015 16:49:55.680526 2866294 api_server.go:162] apiserver freezer: "11:freezer:/docker/b4f192fddfe30d3f5ee79c7d868a1068c68ce2be1735cd3a6b14239bb974d0c8/kubepods/burstable/pod6420297fbd837372c0c69d6daa60b210/07c544ae288c834b821cba907be82d699bfed277d3ce8d5eee845eb66579d82c"
I1015 16:49:55.680731 2866294 ssh_runner.go:148] Run: sudo cat /sys/fs/cgroup/freezer/docker/b4f192fddfe30d3f5ee79c7d868a1068c68ce2be1735cd3a6b14239bb974d0c8/kubepods/burstable/pod6420297fbd837372c0c69d6daa60b210/07c544ae288c834b821cba907be82d699bfed277d3ce8d5eee845eb66579d82c/freezer.state
I1015 16:49:55.693913 2866294 api_server.go:184] freezer state: "THAWED"
I1015 16:49:55.693982 2866294 api_server.go:221] Checking apiserver healthz at https://172.17.0.3:8443/healthz ...
I1015 16:49:55.702640 2866294 api_server.go:241] https://172.17.0.3:8443/healthz returned 200:
ok
W1015 16:49:55.703107 2866294 out.go:145] 🤔 Verifying dashboard health ...
🤔 Verifying dashboard health ...
I1015 16:49:55.720916 2866294 service.go:213] Found service: &Service{ObjectMeta:{kubernetes-dashboard kubernetes-dashboard /api/v1/namespaces/kubernetes-dashboard/services/kubernetes-dashboard 86c9590d-8bf2-4c46-b813-2a34b45181fd 501 0 2020-10-15 16:47:19 +0400 +04 map[addonmanager.kubernetes.io/mode:Reconcile k8s-app:kubernetes-dashboard kubernetes.io/minikube-addons:dashboard] map[kubectl.kubernetes.io/last-applied-configuration:{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"addonmanager.kubernetes.io/mode":"Reconcile","k8s-app":"kubernetes-dashboard","kubernetes.io/minikube-addons":"dashboard"},"name":"kubernetes-dashboard","namespace":"kubernetes-dashboard"},"spec":{"ports":[{"port":80,"targetPort":9090}],"selector":{"k8s-app":"kubernetes-dashboard"}}}
] [] [] [{kubectl-client-side-apply Update v1 2020-10-15 16:47:19 +0400 +04 FieldsV1 FieldsV1{Raw:*[123 34 102 58 109 101 116 97 100 97 116 97 34 58 123 34 102 58 97 110 110 111 116 97 116 105 111 110 115 34 58 123 34 46 34 58 123 125 44 34 102 58 107 117 98 101 99 116 108 46 107 117 98 101 114 110 101 116 101 115 46 105 111 47 108 97 115 116 45 97 112 112 108 105 101 100 45 99 111 110 102 105 103 117 114 97 116 105 111 110 34 58 123 125 125 44 34 102 58 108 97 98 101 108 115 34 58 123 34 46 34 58 123 125 44 34 102 58 97 100 100 111 110 109 97 110 97 103 101 114 46 107 117 98 101 114 110 101 116 101 115 46 105 111 47 109 111 100 101 34 58 123 125 44 34 102 58 107 56 115 45 97 112 112 34 58 123 125 44 34 102 58 107 117 98 101 114 110 101 116 101 115 46 105 111 47 109 105 110 105 107 117 98 101 45 97 100 100 111 110 115 34 58 123 125 125 125 44 34 102 58 115 112 101 99 34 58 123 34 102 58 112 111 114 116 115 34 58 123 34 46 34 58 123 125 44 34 107 58 123 92 34 112 111 114 116 92 34 58 56 48 44 92 34 112 114 111 116 111 99 111 108 92 34 58 92 34 84 67 80 92 34 125 34 58 123 34 46 34 58 123 125 44 34 102 58 112 111 114 116 34 58 123 125 44 34 102 58 112 114 111 116 111 99 111 108 34 58 123 125 44 34 102 58 116 97 114 103 101 116 80 111 114 116 34 58 123 125 125 125 44 34 102 58 115 101 108 101 99 116 111 114 34 58 123 34 46 34 58 123 125 44 34 102 58 107 56 115 45 97 112 112 34 58 123 125 125 44 34 102 58 115 101 115 115 105 111 110 65 102 102 105 110 105 116 121 34 58 123 125 44 34 102 58 116 121 112 101 34 58 123 125 125 125],}}]},Spec:ServiceSpec{Ports:[]ServicePort{ServicePort{Name:,Protocol:TCP,Port:80,TargetPort:{0 9090 },NodePort:0,},},Selector:map[string]string{k8s-app: kubernetes-dashboard,},ClusterIP:10.98.126.49,Type:ClusterIP,ExternalIPs:[],SessionAffinity:None,LoadBalancerIP:,LoadBalancerSourceRanges:[],ExternalName:,ExternalTrafficPolicy:,HealthCheckNodePort:0,PublishNotReadyAddresses:false,SessionAffinityConfig:nil,IPFamily:nil,TopologyKeys:[],},Status:ServiceStatus{LoadBalancer:LoadBalancerStatus{Ingress:[]LoadBalancerIngress{},},},}
W1015 16:49:55.721205 2866294 out.go:145] 🚀 Launching proxy ...
🚀 Launching proxy ...
I1015 16:49:55.721346 2866294 dashboard.go:146] Executing: /snap/bin/kubectl [/snap/bin/kubectl --context minikube proxy --port=0]
I1015 16:49:55.721657 2866294 dashboard.go:151] Waiting for kubectl to output host:port ...
I1015 16:49:55.871044 2866294 out.go:109]
W1015 16:49:55.871207 2866294 out.go:145] ❌ Exiting due to HOST_KUBECTL_PROXY: readByteWithTimeout: EOF
❌ Exiting due to HOST_KUBECTL_PROXY: readByteWithTimeout: EOF
W1015 16:49:55.871274 2866294 out.go:145]
W1015 16:49:55.871352 2866294 out.go:145] 😿 If the above advice does not help, please let us know:
😿 If the above advice does not help, please let us know:
W1015 16:49:55.871407 2866294 out.go:145] 👉 https://github.com/kubernetes/minikube/issues/new/choose
👉 https://github.com/kubernetes/minikube/issues/new/choose
I1015 16:49:55.882998 2866294 out.go:109]
Optional: Full output of
minikube logscommand:The text was updated successfully, but these errors were encountered: