You need Xdebug log to confirm what it is doing. Check this one (not sure if it will help with container though). In those threads where I was suggesting it (and that was ordinary system, not virtual) it was helping. but going to mention it anyway ( sudo setsebool -P httpd_can_network_connect=1 ). I do not think you have SELinux or alike in Docker containers. using fwrite() or alike)? To check that it can write there.Ģ. So I tried /tmp/xdebug but it doesn't work either.ġ. Given that xdebug configs are almost identical between my local server and my Docker container, that Storm debug validation is successful on both servers, that my Storm for the project in Docker catches the xdebug connection when I load the project on my local server (although as an external connection since it's not from the Docker server address), I'm guessing something is lost somewhere inside Docker but I'm not really sure anymore. Here is my xdebug config on Docker container: xdebug xdebug support I run Docker in rootless mode but when I go to Build, Execution, Deployment>Docker and configure my Docker, the connection is successful. When I try to validate my debug configuration in Storm for the docker version, is found and everything is ok. I compared the xdebug configuration in phpinfo between my local server and the container, both are strictly identical (except for remote_host, it's localhost on my local server, and the log paths). Now, when I run the exact same project with Docker, everything works fine but my breakpoint doesn't trigger anything. When I set up PHP>Debug and validate my configuration for xdebug, it is ok.When I enable Chrome xdebug extension and start listening for debug connections in Storm, my breakpoint (at the very start of the page execution) is catched and I can debug. I can run the project on a local apache+php5.6+xdebug2.5.5 and it works fine.
I'm working on a project running on PHP 5.6, with cakePHP.
I'm on ubuntu 20, runing the latest stable PHPStorm.
0 kommentar(er)
