Skip to content

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

Closed

Description

@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.

Cursor_and_testbot-macos-drud1

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. ...

Activity

  1. 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
  2. lorenrh commented on Jul 12, 2021

    @lorenrh
    Member

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

  3. StefanScherer commented on Jul 14, 2021

    @StefanScherer
    Member

    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.

  4. rfay commented on Aug 12, 2021

    @rfay
    Author

    I got this same exact error upgrading from 3.5.2 to 3.6.0

  5. rfay commented on Sep 1, 2021

    @rfay
    Author

    Same exact error upgrading from 3.6.0 to 4.0.0.

  6. rfay commented on Sep 14, 2021

    @rfay
    Author

    Same error upgrading from 4.0.0 to 4.0.1, Apple M1.

    Screen Shot 2021-09-14 at 4 24 24 PM

  7. rfay commented on Sep 30, 2021

    @rfay
    Author

    Same thing upgrading to 4.1.0
    rfay_istweb-content-local-web___var_www_html_docroot_and_rfay_d9-web___var_www_html_and_rfay_d9-web___var_www_html

  8. 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
  9. StefanScherer commented on Oct 1, 2021

    @StefanScherer
    Member

    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.

  10. joe0BAB commented on Nov 9, 2021

    @joe0BAB

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

  11. rfay commented on Nov 9, 2021

    @rfay
    Author

    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?

    Cursor_and_rfay-mba2013-macos

  12. 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
  13. StefanScherer commented on Nov 10, 2021

    @StefanScherer
    Member

    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. 🤞

  14. docker-robott commented on Dec 10, 2021

    @docker-robott
    Collaborator

    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

  15. locked and limited conversation to collaborators on Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions