PHPStorm doesn't work with xdebug + docker, but is ok without docker 关注

debug validation for Docker successful

Hi there,

Enable Xdebug log (restart php/Apache so it sees the new config), try to debug and see what it has to say about it (if Xdebug is connecting and where / if at all).

If Xdebug log is empty/not created: 1) check the path (use absolute path) 2) check file permissions 3) make sure that Xdebug is actually trying to debug (e.g. have xdebug.remote_autostart=1 or xdebug_break(); in PHP code)

debug validation for Docker successful

It just checks the basic settings (that they are present / basic checks). It does not check the actual connectivity (if it can make a connection to the IDE).

P.S. In your case it may not bee needed, but I would switch from default 9000 port to some another (e.g. Xdebug 3 uses 9003) anyway -- to avoid possible issues with php-fpm that also uses that port.

Hi, thanks for helping.

So I set xdebug.remote_enable=1, xdebug.remote_autostart=1, define xdebug.remote_log=/tmp/xdebug. Also I changed the port to 9003.

And I get absolutely no log :(

At first I tried to set the logpath to /var/www/xdebug but I thought maybe there's a permission problem, so I tried /tmp/xdebug but it doesn't work either.

I also tried to place a xdebug_break(); in the code. I'm sure it went through it as it was right before my phpinfo(); which appears on screen.

I'm a bit confused.

so I tried /tmp/xdebug but it doesn't work either.

1. Can your PHP script write there (e.g. using fwrite() or alike)? To check that it can write there...

2. I do not think you have SELinux or alike in Docker containers .. but going to mention it anyway ( sudo setsebool -P httpd_can_network_connect=1 ). In those threads where I was suggesting it (and that was ordinary system, not virtual) it was helping. From https://intellij-support.jetbrains.com/hc/en-us/community/posts/206339279/comments/206899645

3. Check this one (not sure if it will help with container though) -- https://stackoverflow.com/a/63358357/783119

You need Xdebug log to confirm what it is doing.

P.S. Too bad you have to stick to Xdebug v2 -- v3 has easier ways of troubleshooting.

I also tried to place a xdebug_break(); in the code. I'm sure it went through it as it was right before my phpinfo(); which appears on screen.

Always add some unique code that can confirm that it is run on the right system. E.g. print IP or server name etc (something unique that will allow you to differentiate one system from another). That's in case if you are executing the wrong URL or file was not updated there. Just a random thought that helped me in the past.

I run Docker in rootless mode...

This might be related.

This guy is having a similar sort of issue. The mention of "rootless docker" is his last comment. https://stackoverflow.com/questions/70577709/xdebug-3-couldnt-connect-from-docker-20-10-12-to-phpstorm-debug-client-ubunt

No better suggestions from me right now.

Thanks for the links. He mentions rootless docker but at least he seems to have some logs.

In my script I did some file_put_contents() and some fwrite() to /tmp, everything seems fine but in CLI, in my container I can't find the files that are supposed to have been created...

edit even before posting :D :

I can't see these files but as writing doesn't seem to be a problem, I took a wild guess and tried accessing my xdebug log and it worked!! it says:

Log opened at 2022-11-18 15:16:50
I: Connecting to configured address/port: host.docker.internal:9003.
W: Creating socket for 'host.docker.internal:9003', poll success, but error: Operation now in progress (29).
E: Could not connect to client. :-(
Log closed at 2022-11-18 15:16:50

Log opened at 2022-11-18 15:16:51
I: Connecting to configured address/port: host.docker.internal:9003.
W: Creating socket for 'host.docker.internal:9003', poll success, but error: Operation now in progress (29).
E: Could not conn'...

I thought there was a problem with local port 9003 so I tried to switch the xdebug of my non-dockerized project to 9003 and also set Storm to listen to 9003 only, and the break happens. So it's not a 9003 thing.

At least we keep going! thanks

TBH I do not have much concrete ideas (as I'm on Windows, rarely work with Docker and when I do it just works in those images).

Right now it looks like Xdebug cannot make an outgoing connection for some reason.

• Could be how rootless Docker deals with networking (cannot help here at all)
• Some kind of firewall / networking rule
• Could be IPv6 vs Pv4 as well (try sticking to IPv4 to check, see to which IP host.docker.internal is resolved)
• Try using numeric IP instead of host.docker.internal (in case it may point to the wrong address, although you have added the extra_hosts line) -- see ip a kind of output (or whatever you have there)
• Maybe your Docker image has some bad bindings (e.g. a common mistake is to port forward/expose Xdebug port as if it's an incoming connection).
• Are you able to make outgoing connection from inside the docker to your host OS (e.g. call some simple URL on your local test web server or alike -- this kind of thing)
• Make sure that PhpStorm is the process that listen on Xdebug port (on your host OS) and not any other process (unlikely to be an issue here since the local debug works)

I disabled my firewall and host.docker.internal is resolved to my ipv4 address.

Actually I think the issue is about your first point: rootless docker. I found this: https://www.reddit.com/r/docker/comments/vx828k/comment/ifuttc3/ which pretty seems like my problem and lead me to this https://github.com/moby/moby/issues/41904#issuecomment-765144432.

Now it says something about slirp4netns which I don't know what it is. And honestly I'm not a docker or even network genius, so I think I might convene with some coworkers who might be willing to go the next step and figure this out.

I will try to remember this post and update it if things improve.

Anyway, thank you very much for your help, you provided me with a big lead!

Regards

https://stackoverflow.com/q/72402715/783119

Try with the IP address of the host OS (e.g. xdebug.client_host=192.168.178.46 )

Ahah it works!

So I removed a lot of things I added, and the important settings are xdebug.remote_host and xdebug.remote_connect_back=0

xdebug config is now:

xdebug

On Storm side, I ended up having no configuration to do except setting up a local server (PHP/Servers) with host localhost and port 9999, and mapping the project root path to /var/www

And when I open http://localhost:9999 my breakpoints are working!

Thanks a bunch for your precious help!