PHPSTORM XDEBUG NOT WORKING UPDATE
PHPSTORM XDEBUG NOT WORKING PC

To start the project, I just run: WSLIP=$(grep nameserver /etc/nf | cut -d ' ' -f2) docker-compose up In the entry point, I use sed to remove the remote_host line and echo to append new remote_host from the WSLIP environment variable defined in docker-compose.yml. I have chosen to use the environment variable when starting my Docker Compose and changing the entry point for Apache.

PHPSTORM XDEBUG NOT WORKING UPDATE

You can solve this issue in many different ways from changing the remote_host every time it changes manually to update it using the script. ThatвЂ™s why you need to define it dynamically. Problem is, that if you defined this IP address in your Xdebug configuration, it might not work the second time you try to run the project. To stop automatic generation of this file, add the following entry to /etc/wsl.conf: # generateResolvConf = false nameserver 172.22.48.1 You can find this IP in your Linux distro like so $ cat /etc/nf # This file was automatically generated by WSL.

PHPSTORM XDEBUG NOT WORKING PC

Hurdle #3 WSL 2 changes the IP address of Windows host every time you restart your PC (most likely). You might be wondering, why is there no xdebug.remote_host. It is basically xdebug.remote_enable=1 xdebug.remote_handler=dbgp xdebug.remote_port=9005 xdebug.remote_autostart=1 xdebug.remote_connect_back=0 xdebug.idekey=docker Now you need to configure IntelliJ to enable Xdebug support. Having the file on the Windows filesystem will be actually slower than WSL 1.ДЄfter installing the project, you can open the project in IntelliJ using \wsl$ path. Hurdle #2 The important part is that you need to have the source files inside WSL 2 filesystem!! This is described in the Docker best practices.

You can reclaim 10s to 100s of GBs of memory that you wonвЂ™t be able to use anyway after switching to WSL 2 Backend. If you are serious about switching, I recommend you to prune unused Docker objects. Hurdle #1 One thing that made sense but was confusing at first was that after you switch Docker backend to WSL 2, you wonвЂ™t be able to access your images, volumes, and containers, etc. Again, everything is pretty straight forward. Next, you need to switch your Docker Desktop to use WSL 2 Backend. If you want to just test it out and donвЂ™t want to use your own project, you can use my modified demo project on my Github. As an example project, I will use the demo Symfony project with some modifications, but you can use any project you want. It is pretty straight forward, you can follow the instructions here. Prerequisites are that you have WSL 2 with your favorite Linux distribution installed. ThatвЂ™s why I have decided to write this article to share what have I learned when playing with WSL 2 so you donвЂ™t have to figure out things all by yourself. But there were some hurdles along the way that I had to overcome. My goal was simple, I wanted to run the project inside Docker and be able to debug it remotely with Xdebug in IntelliJ. I wanted to try out WSL 2 to see the difference in one of my PHP projects. There were also many other problems like poor IO performance through Samba protocol or missing mapping for some system calls like inotify. With WSL 2, you can enjoy all the benefits even on Windows Home. One of the common problems with Docker on Windows used to be that Windows Home could not run Hyper-V. You can run them with near Linux-like performance even on Windows, which is a big deal and it solves many of the problems of running Docker on Windows. With the release of Docker Desktop WSL 2 Backend, you can greatly improve the performance of your pr ojects.

Phpstorm xdebug not working