Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minikube dashboard #8119

Closed
vasanthakumars98 opened this issue May 13, 2020 · 13 comments · Fixed by #8792
Closed

minikube dashboard #8119

vasanthakumars98 opened this issue May 13, 2020 · 13 comments · Fixed by #8792
Labels
co/dashboard dashboard related issues kind/support Categorizes issue or PR as a support question. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@vasanthakumars98
Copy link

Unable to enable dashboard: running callbacks: [sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.18.0/kubectl apply -f /etc/kubernetes/addons/dashboard-ns.yaml -f /etc/kubernetes/addons/dashboard-clusterrole.yaml -f /etc/kubernetes/addons/dashboard-clusterrolebinding.yaml -f /etc/kubernetes/addons/dashboard-configmap.yaml -f /etc/kubernetes/addons/dashboard-dp.yaml -f /etc/kubernetes/addons/dashboard-role.yaml -f /etc/kubernetes/addons/dashboard-rolebinding.yaml -f /etc/kubernetes/addons/dashboard-sa.yaml -f /etc/kubernetes/addons/dashboard-secret.yaml -f /etc/kubernetes/addons/dashboard-svc.yaml: exec: already started
stdout:

stderr:
]

😿 minikube is exiting due to an error. If the above message is not useful, open an issue:
👉 /~https://github.com/kubernetes/minikube/issues/new/choose

@9kranti
Copy link

9kranti commented May 13, 2020

Try minikube addons enable dashboard

@sharifelgamal
Copy link
Collaborator

Hi @vasanthakumars98, I don’t yet have a clear way to replicate this issue. Do you mind adding some additional details. Here is additional information that would be helpful:

  • The exact minikube start command line used

  • The full output of the minikube start command, preferably with --alsologtostderr -v=4 for extra logging.

  • The full output of minikube logs

  • The full output of kubectl get po -A

  • Your operating system

Thank you for sharing your experience!

@sharifelgamal sharifelgamal added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. kind/support Categorizes issue or PR as a support question. co/dashboard dashboard related issues labels May 13, 2020
@vasanthakumars98
Copy link
Author

hi @sharifelgamal here is it
minikube start --driver=none

NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-66bff467f8-22psb 0/1 Running 0 48m
kube-system coredns-66bff467f8-csvt5 0/1 Running 0 48m
kube-system etcd-vasanth 1/1 Running 0 48m
kube-system kube-apiserver-vasanth 1/1 Running 0 48m
kube-system kube-controller-manager-vasanth 1/1 Running 0 48m
kube-system kube-proxy-w9kfd 1/1 Running 0 48m
kube-system kube-scheduler-vasanth 1/1 Running 0 48m
kube-system storage-provisioner 1/1 Running 0 47m
kubernetes-dashboard dashboard-metrics-scraper-84bfdf55ff-jqvvq 1/1 Running 0 2m11s
kubernetes-dashboard kubernetes-dashboard-bc446cc64-2r2dn 1/1 Running 2 2m11s

opreating-system: ubuntu-version 18

@vasanthakumars98
Copy link
Author

hi @9kranti
i have added adon dashboard and used this commnd minikube dashboard
this is the output
root@vasanth:/home/vasanth/Desktop/k8's# minikube dashboard

🤔 Verifying dashboard health ...
🚀 Launching proxy ...
🤔 Verifying proxy health ...
💣 http://127.0.0.1:38843/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/ is not accessible: Temporary Error: unexpected response code: 503
root@vasanth:/home/vasanth/Desktop/k8's#
root@vasanth:/home/vasanth/Desktop/k8's# minikube dashboard

🤔 Verifying dashboard health ...
🚀 Launching proxy ...
🤔 Verifying proxy health ...
💣 http://127.0.0.1:38843/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/ is not accessible: Temporary Error: unexpected response code: 503
root@vasanth:/home/vasanth/Desktop/k8's#

@9kranti
Copy link

9kranti commented May 14, 2020

Once try with
minikube stop
minikube start
Then go for minikube dashboard

@vasanthakumars98
Copy link
Author

hi @9kranti
i have tried to stop, delete and start many time
eventhough is tried this manny time it wont works i was facing the same problem

@9kranti
Copy link

9kranti commented May 14, 2020

Let's try this,
minikube stop
minikube delete
minikube start --cpus 2 --memory 16g --driver hypervisor_name
In above command please provide name of hypervisor which is installed on your system

@vasanthakumars98
Copy link
Author

hi @9kranti
how to find hypervisor_name
i have just installed virtualbox while installing minikube but am not using that

@9kranti
Copy link

9kranti commented May 15, 2020

You can find the list of hypervisor on Kubernetes's official documentation
In your case hypervisor is VirtualBox
Try below command:
minikube start --cpus 2 --memory 16g --driver virtualbox

@vasanthakumars98
Copy link
Author

hi @9kranti
while using this minikube start --cpus 2 --memory 16g --driver virtualbox
this was the output
🎉 minikube 1.10.1 is available! Download it: /~https://github.com/kubernetes/minikube/releases/tag/v1.10.1
💡 To disable this notice, run: 'minikube config set WantUpdateNotification false'

🙄 minikube v1.9.2 on Ubuntu 18.04
✨ Using the virtualbox driver based on user configuration

❗ 'virtualbox' driver reported an issue: /usr/bin/VBoxManage list hostinfo failed:

💡 Suggestion: Install the latest version of VirtualBox
📘 Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/virtualbox/

🛑 The "virtualbox" driver should not be used with root privileges.
💡 If you are running minikube within a VM, consider using --driver=none:
📘 https://minikube.sigs.k8s.io/docs/reference/drivers/none/

@vasanthakumars98
Copy link
Author

hi @9kranti
cmd: minikube start --cpus 2 --memory 16g --driver=virtualbox --alsologtostderr
output
I0515 15:30:18.513600 23360 start.go:262] hostinfo: {"hostname":"vasanth","uptime":20889,"bootTime":1589515929,"procs":367,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"18.04","kernelVersion":"5.3.0-46-generic","virtualizationSystem":"kvm","virtualizationRole":"host","hostid":"4c4c4544-0033-5710-8038-c6c04f485831"}
I0515 15:30:18.514880 23360 start.go:272] virtualization: kvm host
😄 minikube v1.9.2 on Ubuntu 18.04
I0515 15:30:18.559460 23360 driver.go:245] Setting default libvirt URI to qemu:///system
✨ Using the virtualbox driver based on user configuration
I0515 15:30:18.894400 23360 start.go:310] selected driver: virtualbox
I0515 15:30:18.894472 23360 start.go:656] validating driver "virtualbox" against
I0515 15:30:18.894567 23360 start.go:662] status for virtualbox: {Installed:true Healthy:true Error: Fix: Doc:}
🛑 The "virtualbox" driver should not be used with root privileges.
💡 If you are running minikube within a VM, consider using --driver=none:
📘 https://minikube.sigs.k8s.io/docs/reference/drivers/none/

@vasanthakumars98
Copy link
Author

hi @9kranti
after using this cmd
minikube start --driver=virtualbox --force
it's working
thanks for your help

@afbjorklund
Copy link
Collaborator

Normally you don't log in to your system as root, but use sudo where needed instead.

https://help.ubuntu.com/community/RootSudo

concaf added a commit to concaf/minikube that referenced this issue Jul 21, 2020
Whenever a `kubectl apply` fails while enabling an addon, it is
retried with exponential backoff. The command (type `*exec.Cmd`)
that this retry function runs in created outside the function -
which means that it is reused on every retry. This is a problem
because `exec.Cmd` (https://godoc.org/github.com/pkg/exec#Cmd)
states that "... Cmd cannot be reused after calling its Run or
Start methods."

This retry is a common case due to, say, a CRD and its resource
being present in the same YAML file of the addon which causes
a race condition where the resource is created before its CRD is
created in the cluster - this race is fixed by subsequent retries.
I've noticed this in the dashboard and the ambassador addon.

Due to the above mentioned bug, minikube throws errors like
`exec: already started` in every retry and the retry is never
successful, manifests are never deployed and addon creation errors
out.

Fix kubernetes#8138
Fix kubernetes#8119
Fix a few CI errors in kubernetes#8372
concaf added a commit to concaf/minikube that referenced this issue Jul 21, 2020
Whenever a `kubectl apply` fails while enabling an addon, it is
retried with exponential backoff. The command (type `*exec.Cmd`)
that this retry function runs in created outside the function -
which means that it is reused on every retry. This is a problem
because `exec.Cmd` (https://godoc.org/github.com/pkg/exec#Cmd)
states that "... Cmd cannot be reused after calling its Run or
Start methods."

This retry is a common case due to, say, a CRD and its resource
being present in the same YAML file of the addon which causes
a race condition where the resource is created before its CRD is
created in the cluster - this race is fixed by subsequent retries.
I've noticed this in the dashboard and the ambassador addon.

Due to the above mentioned bug, minikube throws errors like
`exec: already started` in every retry and the retry is never
successful, manifests are never deployed and addon creation errors
out.

Related to kubernetes#8138 kubernetes#8119 kubernetes#8372
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/dashboard dashboard related issues kind/support Categorizes issue or PR as a support question. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants