Closed proteo closed 6 years ago
OK, it looks like the 7.2 branch is the culprit here. After realizing that docker4drupal uses 7.1, I pointed the container to wodby/wordpress:4-7.1-3.3.1 and xdebug works fine now.
Xdebug didn't support 7.2 version last time we updated images
Hi Chingis, thanks for your excellent work. I'm having a small problem with docker4wordpress, hope you can give me a hint.
I've been trying to enable xdebug without success. As you can see in the docker-compose.yml info (at the bottom) the definition includes the required flags, plus the ones required for macOS:
PHP_XDEBUG: 1 PHP_XDEBUG_DEFAULT_ENABLE: 1 PHP_XDEBUG_REMOTE_CONNECT_BACK: 0 PHP_XDEBUG_REMOTE_HOST: "10.254.254.254" PHP_XDEBUG_PROFILER_OUTPUT_DIR: /mnt/files/xdebug/profiler PHP_XDEBUG_TRACE_OUTPUT_DIR: /mnt/files/xdebug/traces
However, my IDE (PHPStorm) can't see the debugger. It looks like no xdebug extension is loaded, since the output of php_info() doesn't include any information about it:
I've tried using one of to other images suggested (like wodby/wordpress-php:7.2-3.3.1), with no luck. Even tried using wodby/php directly –which seems to work fine BTW– but still, it won't load xdebug. As a side note, I've been using your docker4drupal image for a while with fantastic results, and xdebug works just fine there.
Any help will be greatly appreciated, many thanks in advance.
Codebase
Tried both (first with the default named volume, then with my own codebase).
Host OS
macOS Sierra
Docker info output
Docker compose file
Logs output