-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
dashboard as root: Unsupported authorisation protocol / cannot open display: localhost:10.0 #2548
Comments
What browser do you have installed? The minikube dashboard command works by calling "xdg-open" with the correct URL, which is supposed to open your browser to the right page. From that error, it looks like xdg-open is trying to open many different browsers but is unable to find any installed ones. |
Thanks @dlorenc for addressing my query. I am using firefox. I reinstalled it and after some troubleshooting i am able to get minikube dashboard command running correctly but in browser dashboard is not shown instead "unable to connect" message is displayed on http://195.148.127.245:30000/. It also returns some error messages related to permission of configuration files. Do you understand whats the issue here? minikube dashboard |
I too have the same issue |
I am seeing this issue as well on Macbook Pro (latest 10.13..3) - with k8s version 1.7.5. I updated VirtualBox to latest, deleted ~/.minikube, and downloaded v0.25.2. ᐅ minikube start --kubernetes-version v1.7.5
#...
ᐅ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system kube-addon-manager-minikube 1/1 Running 0 35m
kube-system kube-dns-3693656504-0zvlq 3/3 Running 0 35m
ᐅ minikube addons list
- addon-manager: enabled
- coredns: disabled
- dashboard: enabled
- default-storageclass: enabled
- efk: disabled
- freshpod: disabled
- heapster: disabled
- ingress: disabled
- kube-dns: enabled
- registry: disabled
- registry-creds: disabled
- storage-provisioner: enabled
ᐅ minikube addons enable dashboard
dashboard was successfully enabled
ᐅ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system kube-addon-manager-minikube 1/1 Running 0 36m
kube-system kube-dns-3693656504-0zvlq 3/3 Running 0 36m
ᐅ minikube dashboard
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 In earlier minikube versions - I would clearly see the dashboard pod listed in kubectl. If I revert to minikube 0.22.0, without a Hope this info helps |
Same issue. Driver: HyperV Command executed:
|
I am also getting similar error:
I think this might be because i am doing this as a superuser. |
Yeah Also |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Environment:
Issue
What you expected to happen: How to reproduce it :
Output of minikube logs:
Anything else:
|
Closing now that this has been root caused as being due to running as root, but this is really our fault for not mentioning early that minikube should not be run as root. Opened #3138 to address that. |
Hi i just installed minikube on a remote linux machine (Ubuntu 16.04 server version). I am able to start minikube but to see running deployments, minikube dashboard command is reporting some errors like unsupported authorization protocol, missing modules (chrome browser, mozilla etc.). Can anyone tell me how to fix this issue so i can see dashboard on my local pc by accessing : http://192.140.127.45:30000
minikube status
minikube: Running
cluster: Running
kubectl: Correctly Configured: pointing to minikube-vm at 192.140.127.45
kubectl cluster-info
Kubernetes master is running at https://192.140.127.45:8443
root@yx-lab2: minikube dashboard
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...
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...
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...
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...
Opening kubernetes dashboard in default browser...
MobaXterm X11 proxy: Unsupported authorisation protocol
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Broadway display type not supported: localhost:10.0
Error: cannot open display: localhost:10.0
MobaXterm X11 proxy: Unsupported authorisation protocol
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Broadway display type not supported: localhost:10.0
Error: cannot open display: localhost:10.0
MobaXterm X11 proxy: Unsupported authorisation protocol
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Broadway display type not supported: localhost:10.0
Error: cannot open display: localhost:10.0
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: iceweasel: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: seamonkey: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: mozilla: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: epiphany: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: konqueror: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: chromium-browser: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: google-chrome: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: www-browser: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: links2: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: elinks: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: links: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: lynx: not found
/usr/bin/xdg-open: 771: /usr/bin/xdg-open: w3m: not found
xdg-open: no method available for opening 'http://192.140.127.45:30000'
minikube version: v0.25.0
cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
grep DriverName ~/.minikube/machines/minikube/config.json
"DriverName": "none",
The text was updated successfully, but these errors were encountered: