How can I access a service running on WSL2 from inside a Docker container?

user_1692830 0
Viewed 8455

I am using Windows 10 1909 and have installed WSL2, using Ubuntu 20.04, the 19.03.13-beta2 docker version, having installed Docker for Windows Edge version using the WSL2 option. The integration is working pretty great, but I have one issue which I cannot solve.

On the WSL2 instance, there are services running, exposing some ports (3000, 3001, 3002,...). From one of the docker containers, I need to access the services for a specific development scenario (API Gateway), and this I cannot get to work.

I have tried using the WSL2 IP address directly, but then the connect just times out. I have also tried using host.docker.internal, which resolves to something else than the WSL2 IP address, but it still doesn't work.

Is there a special trick I need to pull, or is this kind of routing currently not supported, but will be, or is this for some other reason not possible?

This illustrates what I am trying to achieve:

Accessing WSL2 services from docker container

The other routings work - i.e. I can access all the service ports coming from the node.js processes inside WSL2 from the Windows browser, and also I can access the exposed service ports from the containers both from inside WSL2 and from Windows. It's just this missing link I cannot make work.

wsl-2 docker routes
3 Answers

So what you need to do in the windows machine port forward the port you are running on the WSL machine, this script port forwards the port 4000

netsh interface portproxy delete v4tov4 listenport="4000" # Delete any existing port 4000 forwarding
$wslIp=(wsl -d Ubuntu -e sh -c "ip addr show eth0 | grep 'inet\b' | awk '{print `$2}' | cut -d/ -f1") # Get the private IP of the WSL2 instance
netsh interface portproxy add v4tov4 listenport="4000" connectaddress="$wslIp" connectport="4000"

And on the container docker run command you have to add

--add-host=host.docker.internal:host-gateway

or if you are using docker-compose:

    extra_hosts:
      - "host.docker.internal:host-gateway"

Then inside the container you should be able to curl to

curl host.docker.internal:4000

and get a response!

user_112525380

For what it's worth: This scenario is working if you use the WSL2 subsystem IP address.

It does not work if you use host.docker.internal - this DNS alias is defined in the containers, but it maps to the IP address of the Windows host, not of the WSL2 host, and that routing back inside the WSL2 host does not work.

The reason why this (probably temporarily) did not work is somewhat unclear - I will revisit this answer if the problem should reappear and I manage to track down what the actual problem may have been.

user_16928300

I ran into this problem with the latest Docker Desktop. I rolled it back to 4.2 and it worked.

  • Docker Desktop 4.2
  • Windows 19044.1466
  • Ubuntu 20.04

I have a java service running on a linux local host (accessing the IP address using ifconfig command), my other containers running on docker desktop using the WSL2 based engine, which can communicate to my java service using the IP address.

user_109683230
Related