You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docker fatal error on updating from to 3.5.2... and all up to 4.1.0+: Request failed: GET /analyse/startup-failure failed: no response #5834
changed the title [-]Docker crash on updating from 3.5.1 to 3.5.2[/-][+]Docker fatal error on updating from 3.5.1 to 3.5.2: Request failed: GET /analyze/startup-failure failed: no response[/+]on Jul 11, 2021
The workaround so far is to press "Exit" button in that dialog and start Docker Desktop again. It either does the update then or you walk through "Checking for Updates..." and "Update and restart" in the whale menu. It normally works the second time.
We're tracking that issue internally and will come up with a fix in a future version.
Reacted by Randy Fay, Matthias Glastra, Stephen Kuehl and Ethan Gilchrist
changed the title [-]Docker fatal error on updating from 3.5.1 to 3.5.2: Request failed: GET /analyze/startup-failure failed: no response[/-][+]Docker fatal error on updating from to 3.5.2... and all up to 4.1.0+: Request failed: GET /analyze/startup-failure failed: no response[/+]on Sep 30, 2021
Well, I'm glad you're working on this, but it's definitely not solved. Just saw this upgrading to 4.2.0. Are you saying that this should be fixed in future upgrades, or that I should not have seen this upgrading to 4.2.0?
changed the title [-]Docker fatal error on updating from to 3.5.2... and all up to 4.1.0+: Request failed: GET /analyze/startup-failure failed: no response[/-][+]Docker fatal error on updating from to 3.5.2... and all up to 4.1.0+: Request failed: GET /analyse/startup-failure failed: no response[/+]on Nov 9, 2021
Thanks @rfay, yes it is fixed in 4.2.0, but it only will take effect in future updates. Looking forward to new releases where you don‘t have to go through this again. 🤞
Activity
[-]Docker crash on updating from 3.5.1 to 3.5.2[/-][+]Docker fatal error on updating from 3.5.1 to 3.5.2: Request failed: GET /analyze/startup-failure failed: no response[/+]lorenrh commentedon Jul 12, 2021
Thanks for the report. We are investigating this, and will update the ticket when we have more information.
StefanScherer commentedon Jul 14, 2021
The workaround so far is to press "Exit" button in that dialog and start Docker Desktop again. It either does the update then or you walk through "Checking for Updates..." and "Update and restart" in the whale menu. It normally works the second time.
We're tracking that issue internally and will come up with a fix in a future version.
rfay commentedon Aug 12, 2021
I got this same exact error upgrading from 3.5.2 to 3.6.0
rfay commentedon Sep 1, 2021
Same exact error upgrading from 3.6.0 to 4.0.0.
rfay commentedon Sep 14, 2021
Same error upgrading from 4.0.0 to 4.0.1, Apple M1.
rfay commentedon Sep 30, 2021
Same thing upgrading to 4.1.0

[-]Docker fatal error on updating from 3.5.1 to 3.5.2: Request failed: GET /analyze/startup-failure failed: no response[/-][+]Docker fatal error on updating from to 3.5.2... and all up to 4.1.0+: Request failed: GET /analyze/startup-failure failed: no response[/+]StefanScherer commentedon Oct 1, 2021
Thanks @rfay for the constant reminder. Our internal ticket is still open, I'll speak to the engineering team and try to give it a higher priority.
joe0BAB commentedon Nov 9, 2021
Hi! Please try version 4.2.0. The problem should have been fixed there.
rfay commentedon Nov 9, 2021
Well, I'm glad you're working on this, but it's definitely not solved. Just saw this upgrading to 4.2.0. Are you saying that this should be fixed in future upgrades, or that I should not have seen this upgrading to 4.2.0?
[-]Docker fatal error on updating from to 3.5.2... and all up to 4.1.0+: Request failed: GET /analyze/startup-failure failed: no response[/-][+]Docker fatal error on updating from to 3.5.2... and all up to 4.1.0+: Request failed: GET /analyse/startup-failure failed: no response[/+]StefanScherer commentedon Nov 10, 2021
Thanks @rfay, yes it is fixed in 4.2.0, but it only will take effect in future updates. Looking forward to new releases where you don‘t have to go through this again. 🤞
docker-robott commentedon Dec 10, 2021
Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.
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.
/lifecycle locked