That should work on both Docker Desktop and docker-inside-wsl2. So now I guess the thing to do is to get the nameserver from /etc/nf and use that for. So I assume that's why I thought this was working OK. It seems that my earlier testing of this was corrupted by a whole pile of different '' entries that Docker Desktop had put in /etc/hosts and /c/Windows/System32/drivers/etc/hosts over the years. That seems to work in all cases that I've tested. So the answer in the doc is 'Look at /etc/nf and use the nameserver there. In this situation (PhpStorm running on Windows, but ddev in WSL2) we're talking about 'Accessing Windows networking apps from Linux (host IP)' since PhpStorm is a Windows app that's listening. The official docs about WSL2 networking are at

removed the line with the from /etc/hosts.ddev logs: could not connect to debugging client.installed docker desktop (maybe) but not in use.Xdebug works out of the box If I start my ddev project and activate xdebug. We didn't try to uninstall docker desktop cause of all our active projects. Maybe the problem is that docker desktop is already installed but not in use. ddev always get the wrong IP from the docker bridge network.

I found out that ddev set the wrong IP addresse in my /etc/hosts file inside the ddev web container. Tried: :9003 (through xdebug.client_host/xdebug.client_port) :-(' When I try to use xdebug I got this error:Ĭould not connect to debugging client. I switched from docker desktop to docker inside WSL2.

Download xdebug client_host docker