Xdebug Phpstorm Docker Ubuntu

Docker enables developers to deploy applications inside containers for testing code in an environment identical to production. PhpStorm provides Docker support using the Docker plugin. The plugin is bundled and enabled by default. The Docker plugin is bundled with PhpStorm and activated by default. If the plugin is disabled, enable it on the Settings/Preferences Plugins page as. The major difficulty in getting Xdebug (or Zend Debugger) working with PhpStorm and Docker integration is the correct configuration of the Docker container. In our case we're using a Dockerfile (we've already shown this config earlier and provided links to download it) to configure the container, including Xdebug-specific parameters, such as. Pick the PHP Remote Debug template and click the +on the top left to add a new configuration (don't make the mistake of editing the template). Check 'Filter debug connection by IDE key' and set the IDE key to match the one in your XDebug config (for the above we'd use PHPSTORM). Add a server (the name doesn't matter).

Phpstorm Xdebug Docker
Xdebug Phpstorm Docker Ubuntu 18.04

Setting up Xdebug locally, in vagrant or in docker; Debugging in Phpstorm; You can follow along with the xdebug-example github repository I have used throughout this guide. Setting up Xdebug Xdebug is a PHP extension developed by Derick Rethans for debugging using the DBGp protocol. Xdebug is the only debugging tool to implement the DBGp protocol.

In this post, I’m going to go over my short journey to setup my PHP development environment on Windows 10. I will tell you how to setup PHPStorm to debug PHP applications using XDebug and PHP setup over Ubuntu 18.04 LTS on WSL2. I would like to work against the latest version of PHP and compile it myself. At the same time, setting up extensions and compiling PHP itself on windows is not a very straightforward task as far as I know. The plan is to have the development environment run from Linux (WSL2) while the IDE, which is PHPStorm in our scenario execute from Windows. This way I can make use of the “user friendly” parts and beauty of Windows while still running and debugging my code on Ubuntu.

The significant point about WSL2 is that Windows has now switched to full virtualization to run Linux with a good level of integration between the two operating systems. It’s super easy to work with files from both Windows and Linux and it is much quicker than WSL 1. Moreover, Docker is now fully supported making development much easier.

Let me start by telling you how I got here. I’ve been using Ubuntu for the past couple of years. But then I had to move my computer home because of all this WFH stuff. I soon noticed that my accessories and their drivers work nowhere near as smooth as they do on my Mac. After some digging, I finally decided to go back to Windows. Specifically withWSL2andnative Docker support, I thought this would be the perfect time to give them a try. One week in, I’m satisfied with my decision. But this new setup came with its own set of challenges that I’m going to discuss in this post and share my solutions with you.

Environment Information

Before we go any further, it is wise to discuss what my current setup is. I’m running Windows 10 Education build 19041.172. You need a build later than 18917 to enable WSL2. After following a tutorial[like this one]to enable this feature, which includes joining the insider preview program (which is free), you would need to setup something like Ubuntu 18 from the Windows store.

On my Ubuntu on WSL2, I havedownloaded and compiled PHP 7.4.4along withXDebug 2.9.3. On the Windows side, I have installedPHPStorm.

XDebug Remote Debugging

So the idea is to write PHP code in PHPStorm on Windows and run and debug PHP code on Ubuntu over WSL2. To do that, we need tosetup remote debuggingfor XDebug so that PHPStorm can connect to it and set breakpoints, show variable values and step through the code. I’m going to steal this Gif from XDebug website to show you how this is going to work, understanding this architecture helps you with debugging if you run into an issue during this step:

There is also an option to have XDebug identify the IP address of our IDE through the initial HTTP request (xdebug.remote_connect_back) but unfortunately it does not work under our current setup. I did not get into debugging why that does not work. You can take a look at the packets being transmitted in Wireshark and see what goes wrong. I suspect because both of the machines are running on the same network and some weird translations are being performed by WSL2, maybe the Ubuntu sees Windows host packets as if they are coming from 127.0.0.1. So this is what XDebug configuration looks like inside our php.ini file. You will need to modify the zend_extension path to point to your installation of XDebug. You can also uncomment the last line and create the path to the log file if you need to debug this further:

Setting Up PHPStorm

First, we configure PHPStorm to use XDebug. Under File>Settings>Languages & Frameworks > PHP:

We set the CLI Interpreter to use WSL. It will identify our PHP installation and also tell us that Xdebug is available.

Under Debug, we enable Xdebug and also uncheck the “Pass required config options through command line” under Advanced settings. (This option will pass XDebug configurations through the CLI and override the configurations we have in php.ini)

Finally, to run our script, we need a Run/Debug configuration. Notice that we set interpreter options to“-dxdebug.remote_host=wsl2.host”. This is where we tell XDebug what our IP address of the Windows host machine is, to get that debug connection back. Keep this detail in mind, we’ll get back to it.

Windows WSL2 IP Address

Notice how we need to give Windows IP address to XDebug so that it can connect back to PHPStorm. The thing with WSL2, at least in its current form is that the IP range will totally change during reboots. Let’s say the IP range of the network of WSL2 is currently in the range of “172.30.0.1″, the next time you reboot the machine, and its gonna happen with a Windows machine, the IP address will be in the range of “172.16.14.1”. So we need a way to identify this IP address after each reboot. Ideally, a dynamic entry in hosts file that will map“wsl2.host”to this IP address. This way, we don’t have to update our PHPStorm configuration with the correct IP address every time.

My solution is to run a .Net Core application after each reboot. This small application will read the new IP address of Windows WSL2 interface and update the hosts file entry accordingly. The source code is available here:https://github.com/silverfoxy/wsl2_host_ip.

Download therelease buildof this program. Put it under “Program Files”, and create task under Windows Task Scheduler to run this program withelevated privileges (To update the hosts file) after each login and the action is to run a program which points to our executable.

Now this will add an entry to the Windows hosts file named “wsl2.host“. Recall that we used this host name earlier in our PHPStorm configuration that is passed through the command line to XDebug so that it can connect back from WSL2 Linux VM to our Windows host machine.

This way, we can use our setup and develop PHP applications on Windows while debugging them against the latest version of PHP on Linux. You can verify this by setting a breakpoint in PHPStorm and the breakpoint should pause the execution. Yaaaay!!

Using X11 Forwarding (Everything Runs on Linux)

There is also an easier way to do this which I briefly introduce. The idea is to use X11 forwarding, install everything (PHP, XDebug, PHPStorm) on Linux and just use the UI on Windows. This also works well, and was not perceivably slower. It feels like the fonts are rendered slightly pixely, but I’m not sure if this is truly the case or just a bias between Windows and Ubuntu fonts for PHPStorm. But after all this is an easier setup. I usedVcXsrvfor X11 forwarding on Windows and it works well.

Phpstorm Xdebug Docker