GitHub Down, Docker Desktop Update Broke Everything, DO NOT INSTALL!

Docker Desktop
1

With GitHub being down, it screwed up my docker desktop update. I am fully down now.
I will re-install once github is backup. Hopefully it works then…

2

Hi!
What exactly failed during the Docker Desktop update? Did the update itself fail, or is Docker Desktop now unable to start?

If you can share the Docker Desktop version and the error message you’re seeing, it would be easier to understand whether the update caused the issue or if it’s related to the GitHub outage.

I’d avoid reinstalling for now, especially if you have local containers, volumes or images you need to keep.

3

There is indeed an incident today (August 17th 2026): https://www.githubstatus.com.
Can you share why you feel a GitHub incident would be related to Docker Desktop?

Downloads from https://docs.docker.com/desktop/setup/install/mac-install/ (also for Win and Linux) and https://docs.docker.com/desktop/release-notes/ seem to work.

I just updated successfully from 4.86.0 to 4.87.0 using the DD dashboard’s internal update mechanism (though, I tested it on a Mac).

Do you mind sharing what “Docker Desktop Update Broke Everything” means exactly? If the dashboard starts, can you check which Virtual Machine Manager is configured in Settings → General → Section Virtual Machine Options?

4

I can confirm I suffered the same issues when selecting Docker VMM rather than the usual WSL2 that i was used to using on Windows 11 Pro

5

Since I am not sure what the exact issue of the op was, I am not sure if you had the same issue.

I tried Docker VMM on my Windows laptop after upgrading to 4.78: it worked. Then I removed Docker Desktop (and additionally uninstalled everything related to WSL2/Hyper-V) and tried a user installation of Docker Desktop, which worked as well, but Docker Desktop welcomed me with “No supported Hypervisor detected” (or something along the lines), I had to configure Docker VMM manually. I am not sure if this is a leftover configuration from the previous installation. I was able to run container payloads in both scenarios.

Since it didn’t work for you, your diagnostic data might be interesting for the devs, to maybe find out what caused this behaviour on your system. You can upload the diagnostic with this command (if it works):

 docker desktop diagnose --upload

Could you also create an issue in the Docker Desktop feedback repository?

Please share what exactly happened after you selected Docker VMM, and share the diagnostic id created for the upload.