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

[rfay]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: D18F7D40-640E-4A7A-B066-68B034F7E8BA/20210711130810

Expected behavior

Normal upgrade

Actual behavior

Fatal Error: "Request failed: GET /analyze/startup-failure failed: no response"

I'm pretty sure I saw this on every one of 5 upgrades of macOS test runners and my own computer.

If you click the "Exit" button it seems to continue and finish the upgrade successfully.

I think I saw this on the 3.5.0->3.5.1 upgrade as well, just didn't stop to analyze and report it.

Information

• macOS Version: Big Sur and Catalina
• Intel chip or Apple chip:both
• Docker Desktop Version: 3.5.1 upgrade to 3.5.2

Steps to reproduce the behavior

1. ...
2. ...

[lorenrh]

Thanks for the report. We are investigating this, and will update the ticket when we have more information.

[StefanScherer]

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]

I got this same exact error upgrading from 3.5.2 to 3.6.0

[rfay]

Same exact error upgrading from 3.6.0 to 4.0.0.

[rfay]

Same error upgrading from 4.0.0 to 4.0.1, Apple M1.

[rfay]

Same thing upgrading to 4.1.0

[StefanScherer]

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]

Hi! Please try version 4.2.0. The problem should have been fixed there.

[rfay]

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?