ddev: Misconfigured Docker proxy settings can break ddev healthchecks

Full Gist Diagnostic

After upgrading from v1.16.7 to v1.17.7, the ddev-router does not work anymore. DDev is running on a VirtualBox Debian 10 buster behind a LAN proxy.

ddev-router failed to become ready; debug with 'docker logs ddev-router'; logOutput=, err=health check timed out: labels map[com.docker.compose.service:ddev-router] timed out without becoming healthy, status=

1. Install a VirtualBox VM with Debian 10 Buster
2. Configure proxy.
3. Create DDev config
4. Start DDev

It’s not possible to downgrade, as ddev-homebrew is not versioned.

Expected behavior The DDev containers start up and work just fine.

Version and configuration information (please complete the following information):

• Windows 10 with VirtualBox and Debian 10 Buster
• 1.17.7
• php and mysql project config
• no custom config
• LAN proxy to route through (I cannot get rid of that one, so don’t “fix” it by suggesting it)

Additional context It would have been more helpful for users if the Homebrew receipt would copy the versioning from the main project so that brew versioning could be utilized properly to work around untested new versions.