-
-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have to restart ddev and kill docker-icontainer manually, to make ddev work again. #6216
Comments
It sounds like you have a problem with Docker Desktop; Windows trouble with Docker Desktop is common.
I'd much rather help you get xdebug going using WSL2 + docker-ce. If you come to Discord we can help with that, including doing a screenshare session if needed. https://discord.gg/5wjP76mBJD |
Thank you for your effort and your time. I have stopped the usage of docker-desktop. I unloaded the docker-desktop and use now docker on wsl2 now.
I hope, the new variation will work more properly. I close this issue. If I have problems with the new variation, I will open a new issue. |
Wrong button. |
The PhpStorm extension (and PhpStorm 2024) are having some trouble, but explains how to manually install the extension. |
@Padina42 I've spent an enormous amount of time trying to make WSL2 properly figure out the |
Preliminary checklist
ddev debug test
to include output belowOutput of
ddev debug test
Expand `ddev debug test` diagnostic information
Expected Behavior
I start the php-system with ddev and can develop an extension for TYPO3 using xdebug. The Docker/ddev-system did not need any restart, while i am using it.
Actual Behavior
I use DDEV on windows 11. (no WSL2, because i did not get xdebug/phpstorm to work)
After starting ddev works fine for a while.
After some time I will try an request, but the ddev system won't respond.
The container in Docker Desktop shows low activity. (0,0..%)
Then I have to kill the containers in docker-desktop and I have restart the docker and the ddev.
A
ddev restart
won't work in this cases.After the full restart of docker and ddev everything work fine and fast - until the next crash.
I have not find any systematic for this bug.
Steps To Reproduce
I have currently no idea, how to reproduce that behaviour.
Anything else?
No response
The text was updated successfully, but these errors were encountered: