Came across an issue several weeks ago where I was running into minikube ip = 127.0.0.1. Never sorted it out, thought I'd give it another shot. Now I'm getting minikube ip = 172.17.0.2 and running into similar issues.

Basically, can't connect in browser to 172.17.0.2 as the connection times out. This was not an issue a couple months ago and just start occurring within the past 3-4 weeks.

• Using WSL2 (Ubuntu 18.04)
• docker, kubectl, minikube, skaffold all in WSL2 (i.e., no Docker for Windows)
• Using --driver=docker because that is the only thing that works in WSL2
• minikube ip is 172.17.0.2
• ingress controller is operating normally for minikube
• Tried connecting to port 2376

How am I supposed to connect to this cluster running in minikube with this IP?

EDIT

In all cases (macOS, Ubuntu, WSL2), I'm using skaffold to start to the cluster and using ingress-nginx to handle traffic. So this is likely an issue unique to using --driver=docker, and because that is the only driver that works for WSL2, it makes WSL2 useless for me as I don't know what the work around is.

In macOS (--driver=hyperkit), or Ubuntu (--driver=kvm2), the steps are pretty straight forward:

minikube start
minikube ip

In browser, you navigate to the IP provided by minikube ip and it just works. This IP address never is 172.17.0.2 or 127.0.0.1.

With WSL2 (--driver=docker because --driver=none or any VM driver does not work), that is apparently not the case:

sudo service docker start
minikube start
minikube ip

minikube ip provides this 172.17.0.2. As I understand it, this is the Docker service IP. So when you navigate to it from a browser, it spins and spins, and eventually times out.

Perhaps there is an extra set of commands to get this working in WSL2, but I'm just running the commands I normally run in macOS or Ubuntu.

So how are you supposed to connect to the cluster from browser to view the running application?