Doctor wont start after install

[rimelek (Ákos Takács)]

@stuartcornes

Just tried to install doctor on a AWS

Doctor who? I guess it was a typo, but if I think about it, Docker is like a doctor sometimes

I moved the topic from the Docker Hub category to Docker Desktop for Windows, since you don’t have a problem with Docker Hub. I also edited your post to use code block. Please, format your post according to the below instructions next time:

How to format your forum posts

The Docker forum is using Discourse, which supports several ways to format your posts: Markdown; see commonmark.org/help for an interactive tutorial BBCode A small selection of HTML Any combination of the above Blank lines for formatting and readability Quite often you’ll need an empty line above specific formatting to make it work. You also need to type blank lines to create proper paragraphs; just pressing Return once and then typing a new block of text right below a previous block only…

Back to the question:

Docker Desktop is not for Windows Server, especially not for Windows Server 2012. Even if it could work, you would need “Nested virtualization” since Docker Desktop creates a virtual machine. Here is a good summary from @vrapolinario about what you could do

License on Windows

Jus to add to @rimelek info: Windows Server can run Windows containers. However, you can’t run Docker Desktop. Instead, you can run Docker CE (community supported, includes CLI), Mirantis Container runtime (commercial use, requires a MCR license), or ContainerD (community supported, does not include CLI). Microsoft has created scripts to install both Docker CE (aka Moby) and ContainerD. The scripts will install everything you need to get it working, but keep in mind that the containerD one also…

Note that you need at least Windows Server 2016

Windows container requirements

If you want to run Linux containers, you need at least a virtual machine. There is no other way.