You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently there is only linux, mac, and windows tutorial for configuring XDebug to get that working properly. Long story short me and my team struggled how to configure xdebug.client_host based on linux/windows tutorial shown in the docs. VSCode running remote in WSL2 for example, it will use the hostname from the WSL2 instead of the localhost or docker.for.lin.internal host.
So i guess we should add more instruction to make sure people using WSL2 backend docker uses the hostname of the WSL instead for the xdebug.client_host configuration. You can get that information through command line:
wsl> hostname -I
What is missing in the documentation?
Information, WSL2 backend for Docker users should use WSL2 hostname for the xdebug.client_host, and the hostname could be retrieved from:
wsl> hostname -I
Are you willing to provide a PR to address this?
No response
The text was updated successfully, but these errors were encountered:
What is wrong in the documentation?
Apparently there is only linux, mac, and windows tutorial for configuring XDebug to get that working properly. Long story short me and my team struggled how to configure xdebug.client_host based on linux/windows tutorial shown in the docs. VSCode running remote in WSL2 for example, it will use the hostname from the WSL2 instead of the localhost or docker.for.lin.internal host.
So i guess we should add more instruction to make sure people using WSL2 backend docker uses the hostname of the WSL instead for the xdebug.client_host configuration. You can get that information through command line:
wsl> hostname -I
What is missing in the documentation?
Information, WSL2 backend for Docker users should use WSL2 hostname for the xdebug.client_host, and the hostname could be retrieved from:
wsl> hostname -I
Are you willing to provide a PR to address this?
No response
The text was updated successfully, but these errors were encountered: