Running the installer for Docker Desktop 2.2.0.0 (downloaded from hub.docker.com) as administrator.
On the wizard screen titled Configuration, leave all default options selected.
Unpacking occurs and then eventually an error is displayed
"Installation failed
Failed to start service: The service did not respond to the start or control request in a timely fashion as CommunityInstaller.ServiceActio.d__37.MoveNext()
Closing the wizard removes all installed files and leaves the c:\Program Files\Docker fodler empty. Rebooting removeds the orphaned service entry.
I have tried this several times and verified that the Hyper-V and Containers Windows Features are enabled.
I have exactly the same issue as the original post, with Docker Desktop 2.2.0.3 installation on Windows 10 Enterprise, and all prerequisites are met. Could anyone help?
I went back and took another look at the prerequisites. One of them was…
64 bit processor with Second Level Address Translation (SLAT)
It turns out that my processor did not support this. The following link discusses how you can tell if your processor supports SLAT. I know I had Docker installed at one time, perhaps about a year ago. Does anyone know the last build that didn’t require SLAT?
means that you don’t have SLAT. The Docker documentation says you have to have it so I’m guessing that was the reason. I was able to go back and install the release dated 2019-02-15. Give that a try. Hope that works for you.
coreinfo.exe might provide the wrong information. If Hyper-V is enabled, it will show EPT as missing due to how Hyper-V works, even if the underlying Hardware supports SLAT. It shows the computer I have that was running docker from the beginning without issues was missing it.
I had the exact same issue with the same error message on trying to install docker on a VMWare Windows VM.
The problem stemmed from the com.docker.service Service (I think the service is called that at least) running into a timeout while being started. I increased the time until a service that is being started is timed out as described here. That fixed the issue