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 crashes unless minikube started #6324

Closed
afbjorklund opened this issue Jan 15, 2020 · 2 comments · Fixed by #6325
Closed

minikube dashboard crashes unless minikube started #6324

afbjorklund opened this issue Jan 15, 2020 · 2 comments · Fixed by #6325
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented Jan 15, 2020

The exact command to reproduce the issue:

minikube delete
minikube dashboard

The full output of the command that failed:

$ minikube dashboard
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x13cee62]
@ensonic
Copy link
Contributor

ensonic commented Feb 24, 2020

I just tested with 1.7.3 and it still crashes:

minikube dashboard
🔌  Enabling dashboard ...

💣  Unable to enable dashboard: running callbacks: [error creating file at /etc/kubernetes/addons/dashboard-ns.yaml: open /etc/kubernetes/addons/dashboard-ns.yaml: permission denied]

😿  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
sudo minikube dashboard
🙄  "minikube" profile does not exist

@ensonic
Copy link
Contributor

ensonic commented Feb 24, 2020

False alarm, we need to pass the same envvars that we gave to minikube start to minikube dashboard too (eg. MINIKUBE_HOME=$HOME CHANGE_MINIKUBE_NONE_USER=true KUBECONFIG=$HOME/.kube/config).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants