add documentation for WSL2

[cheslijones]

1. minikube start --driver=docker
2. minikube ip = 172.17.0.2

How are you supposed to access the web app from a browser when the IP is 172.17.0.2? Browser just spins for a while before saying it can't connect. Only occurs when --driver=docker. Just about every other driver gives you an ip that is accessible from browser.

[tstromberg]

If you are on Docker for macOS or Docker for Windows, networking works a bit differently, as there is no direct IP connectivity to the container. On these platforms, Docker requires individual ports to be proxied through.

See the Deploy applications section of https://minikube.sigs.k8s.io/docs/start/ for instructions on how to get access to your service. Please let me know if this helps!

[cheslijones]

Sorry, I should have specified I'm experimenting with WSL2 and installing docker, kubectl, minikube, and skaffold directly into it and not using Docker for Windows.

I followed the steps in that I basically copied and pasted all of them and was still unable to get any kind of contact between the cluster and browser.

$ kubectl get all
NAME                                  READY   STATUS    RESTARTS   AGE
pod/balanced-77b47f955f-z8z44         1/1     Running   0          2m26s
pod/hello-minikube-5655c9d946-t6fh6   1/1     Running   0          5m31s

NAME                     TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)          AGE
service/balanced         LoadBalancer   10.107.211.77   10.107.211.77   8000:31796/TCP   2m20s
service/hello-minikube   NodePort       10.107.31.112   <none>          8080:32498/TCP   5m26s
service/kubernetes       ClusterIP      10.96.0.1       <none>          443/TCP          22m

NAME                             READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/balanced         1/1     1            1           2m26s
deployment.apps/hello-minikube   1/1     1            1           5m31s

NAME                                        DESIRED   CURRENT   READY   AGE
replicaset.apps/balanced-77b47f955f         1         1         1       2m26s
replicaset.apps/hello-minikube-5655c9d946   1         1         1       5m31s

When I did the hello-minikube examples it gave:

$ minikube service hello-minikube
|-----------|----------------|-------------|-------------------------|
| NAMESPACE |      NAME      | TARGET PORT |           URL           |
|-----------|----------------|-------------|-------------------------|
| default   | hello-minikube |        8080 | http://172.17.0.2:32498 |
|-----------|----------------|-------------|-------------------------|
🎉  Opening service default/hello-minikube in default browser...
👉  http://172.17.0.2:32498

The balanced examples gave me 10.107.211.77. In both cases, the browser eventually just said "Hmmmm.... can't reach this page".

If I could get the examples to work, I could more than likely figure out how to apply this to my ingress controller for my actual application.

[winhtaikaung]

I am facing this too

[cheslijones]

@winhtaikaung Any luck on your end? If not, would love to hear from a dev or someone who knows how to get around this issue.

[afbjorklund]

Like stated above, this is different when running on Mac or Win - the IP is accessible on Linux...

This is a Docker VM limitation, unfortunately. You might also want to try other minikube drivers ?

https://docs.docker.com/docker-for-mac/networking/#known-limitations-use-cases-and-workarounds

https://docs.docker.com/docker-for-windows/networking/#known-limitations-use-cases-and-workarounds

[cheslijones]

There are no other minikube driver choices for WSL2. You can't have virtualization in WSL2 so scratch kvm2, vmware, hyperv, virtualbox, etc. none doesn't work either. Pretty much just leaves docker.

To expand on "none doesn't work either"...

$ sudo minikube start --driver=none --kubernetes-version=1.15.10
😄  minikube v1.9.2 on Ubuntu 20.04
✨  Using the none driver based on existing profile
👍  Kubernetes 1.18.0 is now available. If you would like to upgrade, specify: --kubernetes-version=1.18.0
👍  Starting control plane node  in cluster minikube
🔄  Restarting existing none bare metal machine for "minikube" ...
ℹ️  OS release is Ubuntu 20.04 LTS

❌  [NONE_DOCKER_EXIT_1] Failed to enable container runtime enable docker.: sudo systemctl start docker: exit status 1
stdout:

stderr:
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

💡  Suggestion: Either systemctl is not installed, or Docker is broken. Run 'sudo systemctl start docker' and 'journalctl -u docker'
📘  Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/none
⁉️   Related issue: https://github.com/kubernetes/minikube/issues/4498

$ sudo systemctl start docker
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Docker is running, by the way... so the error makes no sense.

[afbjorklund]

There are no other minikube driver choices for WSL2. You can't have virtualization in WSL2 so scratch kvm2, vmware, hyperv, virtualbox, etc. none doesn't work either. Pretty much just leaves docker.

WSL (1 is container, 2 is vm) is a little like LXD, it will take more effort to get minikube working there.

See #5392 for details.

The error seems to be due to WSL2 not using systemd, can probably be worked around ? #6954

Sorry for missing "WSL"