Expose dashboard for --vm-driver=none

[chmielas]

BUG REPORT

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.24.1

• OS (e.g. from /etc/os-release): 16.04.3 LTS (Xenial Xerus)
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): "none"
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): none
• Install tools:
• Others:
  minikube dashboard --url
  http://127.0.0.1:30000

netstat -tulpn

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:10248         0.0.0.0:*               LISTEN      9643/localkube  
tcp        0      0 127.0.0.1:2379          0.0.0.0:*               LISTEN      9643/localkube  
tcp        0      0 127.0.0.1:2380          0.0.0.0:*               LISTEN      9643/localkube  
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      969/sshd        
tcp6       0      0 :::10250                :::*                    LISTEN      9643/localkube  
tcp6       0      0 :::30443                :::*                    LISTEN      9643/localkube  
tcp6       0      0 :::10251                :::*                    LISTEN      9643/localkube  
tcp6       0      0 :::10252                :::*                    LISTEN      9643/localkube  
tcp6       0      0 :::10255                :::*                    LISTEN      9643/localkube  
tcp6       0      0 :::30000                :::*                    LISTEN      9643/localkube  
tcp6       0      0 :::22                   :::*                    LISTEN      969/sshd        
tcp6       0      0 :::8443                 :::*                    LISTEN      9643/localkube  
tcp6       0      0 :::4194                 :::*                    LISTEN      9643/localkube  
udp        0      0 0.0.0.0:68              0.0.0.0:*                           893/dhclient  

What happened:
When I start minikube with --vm-driver=none ipaddress is always assigned to loopback interface.
What you expected to happen:
Is the way to start minikube and assign interface to different one for example ens3 ?
Without this I cannot expose dashboard outside host maschine. Or maybe is there different, proper way to expose dashboard

How to reproduce it (as minimally and precisely as possible):
minikube start --vm-driver=none
netstat -tulpn

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[asnowfix]

/remove-lifecycle stale

[gandelman-a]

Just hit this, too. Hopping in through a local ssh port forward as follows works, but would be nice to specify a listening addr for the dashboard.

(minikube VM @ 10.0.0.154)
$ minikube dashboard --url

(host machine)
$ ssh -L 8081:localhost:30000 adam@10.0.0.154

surf to http://localhost:8081

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[TimZaman]

Still an issue

[limbuu]

Starting minikube as :
sudo minikube start --vm-driver=none doesnt expose dashoard and give 503 issue.
But, running minikube with VM as:
minikube start --vm-driver=virtual box expose dashboard without issue.

How to expose dashboard in no driver condition???
Minikube version : v1.7
Kubernetes version: v1.17.3
OS: Linux: Ubuntu 16.04

[afbjorklund]

@limbuu : please open a new issue, thanks. Too many changes to dashboard since this one.