Open muirehenwedd opened 1 year ago
You can generate a diagnostics from either Docker Desktop or the terminal : https://docs.docker.com/desktop/troubleshoot/overview/
Hi,
I was having a similar issue with my docker, and searched everywhere for a solution. I first went to Hyper-V manger (can be found by searching in the task bar) and made sure "DockerDesktopVM" was running by right clicking and then pressing connect. Then afterwards, I still was having trouble connecting, but I knew it was no longer a Hyper-V issue. I restarted my machine and did the same step and I was still getting that error. Then what made it work was I went into service.msc, stopped both "Docker Desktop Service" and "Docker Engine". afterwards, I started Docker Desktop, it threw an error saying docker engine was not running, went back to the services.msc window, started both Docker Engine and Docker Desktop Service and it finally started to work.
You can generate a diagnostics from either Docker Desktop or the terminal : https://docs.docker.com/desktop/troubleshoot/overview/
Diagnostics ID: 2A5BF5C9-E3D4-4125-A87D-D43DC22531CE/20231006100942
Description
After the click on the docker desktop icon, nothin happens.
Reproduce
Expected behavior
Docker is started properly.
docker version
docker info
Diagnostics ID
I dont have tools to generate diagnostics id.
Additional Info
Log file content (C:\Users\Maksym\AppData\Local\Docker\log.txt): log.txt