ddev xdebug and other commands that may start DDEV can cause an unexpected restart if people have containers around with DDEV's labels, but that DDEV didn't create.

See Discord thread

Here the OP had PhpStorm misconfigured so it created a new container for each tool use, so they were all left dead. However, they were using ~/.ddev/bin/docker-compose -f .ddev/.ddev-docker-compose-full.yaml, so had our labels on them. But when Phpstorm runs them it doesn't delete after.

So after they used PhpStorm this way, running something like ddev xdebug would check to see if the project was all healthy, find that it was not, and restart.

We'd like not to be sensitive to this PhpStorm failure or similar ones from other tools.