-
Notifications
You must be signed in to change notification settings - Fork 289
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
Stop infinite retry when WSL raised error #8968
Comments
@simonferquel Any comments? |
This is actually something we recently fixed, but it is not yet released. |
how do you fixed it? re-try a limited number of times, re-try wait and re-try? |
We previously had a limitation in our architecture that made it mandatory to have a retry loop there as the backend startup and distro integration logic where controlled from 2 different processes that did not communicate together. We changed all that, and thus we know exactly when to trigger the integration logic within the backend startup code. The fix will appear in next Edge version. When the integration process fail, you'll now have a native Windows notification asking you if you want to restart the integration process or not. |
The issue has been fixed in Edge release 2.4.2.0, thank you for reporting it. |
Actually, I got this particular notification since the latest release and to be honest, I did not know how to fix this. There is no information visible on what to do. I was lucky that I read the release notes to remember something like this restarting issue notification. This way I had a breadcrumb to follow into this issue and finally read the one information that actually helped:
I do use Alpine for by main WSL2 distro. So only now I know I should switch. Thus, I suggest the following: Thanks! :-) |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Hello,
I'm from Microsoft and working on WSL, and from WSL measures, I found that likely Docker Desktop is doing infinite retry if WSL has problem on the user machines(For example, lxss manager crashes, have problem to create virtual networking, WSL bugs...)
On specific devices, WSL is launched more than 50,000 times per day but always failing with error. And I guess it's because that docker desktop is retrying.
I'm not on that machine, but those machine should be very busy to try on an unrecoverable WSL error, and also complains that docker desktop doesn't work but don't know why.
If docker has infinite retry, I would suggest you to just retry a small number of times, if it reached the threshold, just raise a message that WSL have problem, and please fix it first
The text was updated successfully, but these errors were encountered: