skyred / drupal-devcontainers Goto Github PK

Probably since 1.61, the containers created by vscode automatically copy these from host machine, resulting connection failure inside the containers.

HTTPS_PROXY=
HTTP_PROXY=
https_proxy=
http_proxy=

The upstream Drupal docker library uses the composer default web folder name as the web-root. So if a project has a custom web-root, the current way to get around with it is to create a system link.

ln -s ./docroot/ web

But, we'd like to automate this.

With the current version (running phpunit as www-data and standard error path is set):

If xdebug client is not active/turn on, then the error message doesn't print to console as well as /var/log/php_error.log. Instead, xdebug warning like:

Xdebug: [Step Debug] Could not connect to debugging client. Tried: host.docker.internal:9003 (fallback through xdebug.client_host/xdebug.client_port) :-(

is printed to both console and /var/log/php_error.log

Comparing to:

• If xdebug client is active, then functional test error message prints fine, break points also work well
• If the test is kernel, then the error message prints fine no matter if the xdebug client is active or not.

Workaround for now:

1. Turn on xdebug client, set or unset breakpoints would work. Easy.
2. Turn off xdebug serve side in the container (';xdebug.mode=debug' in /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini), but this would debugging functional test from working.

A new bug comes up since xdebug/vscode-php-debug#601 in vscode 1.62

The setting in container is not respected anymore, so the developer has to manually set it again in host (User) profile.