was broken again, unless I added the php.ini with the correct IP.we scheduled the call and I uninstalled Docker Desktop and moved to WSL2 with docker inside again.upgraded WSL2 to the latest preview release because of issues with the latest stable + Docker Desktop.panicked and reverted back to Docker Desktop as I desperately needed xdebug to work.uninstalled Docker Desktop and moved to WSL2 + Docker CE Inside Install Script (this is where it started breaking and I reported my issue in this ticket).migrated to ddev apt package and uninstalled brew version.originally Docker Desktop + linux homebrew ddev install.If it helps, here a brief history/timeline of my ddev/WSL2 setup: Unfortunately after reverting back to the docker desktop install method I wasn't able to reproduce this anymore after switching back again to WSL2 witch docker inside. I faintly remember having multiple IPs returned by ( I think) wsl hostname -I and ddev taking the wrong one. Unfortunately I caught this at a very busy time and I haven't been as helpful on this as I wanted to be - I'm sorry about that. it works fine now, without any extra configuration on your system? I should have taken notes when we looked at this, but I know that was not the same as what was in your nf when we looked at it. Please report it if you 're using an official release build. This usually means you have a locally-built ddev binary or one from a PR build. Instrumentation is opted in, but SegmentKey is not available. Testing to see if /mnt/ddev_config is properly mountedĬopied /home/beb/.ddev/traefik:CopyIntoVolume_lpewvzoogsgy into /mnt/v/traefik in 123.681776msĬopied global traefik config in /home/beb/.ddev/traefik/certs to ddev-global-cache/traefik VIRTUAL_HOST= for webĬopied /home/beb/ddev-debug/.ddev/traefik:CopyIntoVolume_xwbwdbpppmfo into /mnt/v/traefik in 184.705397msĮxec chown -R 1000 /mnt/v/traefik stdout=, stderr=, err= Ĭopied traefik certs in /home/beb/ddev-debug/.ddev/traefik/certs to ddev-global-cache/traefik Pushed mkcert rootca certs to ddev-global-cache/mkcert Pulling image for drud/ddev-dbserver-mariadb-10.4:v1.21.5Įxecuting docker-compose -f /home/beb/ddev-debug/.ddev/.ddev-docker-compose-full.yaml up -build -dĬopied /mnt/c/Users/b.berger/AppData/Local/mkcert:CopyIntoVolume_xkxgmencwfyx into /mnt/v/mkcert in 199.218163msĮxec chown -R 1000 /mnt/v/mkcert stdout=, stderr=, err= = '172.27.48.1 ' because IsWSL2 and !IsDockerDesktop received from nf To stop automatic generation of this file, add the following entry to /etc/wsl.conf: # generateResolvConf = false nf= # This file was automatically generated by WSL. Pulling image for drud/ddev-ssh-agent:v1.21.5 Pulling image for drud/ddev-webserver:20230315_drush8 Then the current derivation (using inspection of the docker bridge) is correct. The situation where people are running the linux version of PhpStorm or another IDE inside WSL2.ddev uses host ip address for, doesn't work with vscode language server #3781 - where the should be 127.0.0.1.The problem is that there are at least two cases that aren't covered yet: 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |