Docker on Windows Server: Setup Guide

Running Docker on Windows Server works natively: Windows Server 2016 through 2025 can host Windows containers, and Microsoft provides a PowerShell script that enables the Containers feature and installs the Docker engine in a few minutes. Docker Desktop is not the tool here; it targets Windows 10 and 11. On a server you use Docker CE (the open-source Moby engine), Mirantis Container Runtime or containerd.

This guide covers the requirements, installation, your first container, isolation modes and the licensing rules for Standard and Datacenter.

Can You Run Docker on Windows Server?

Yes. Windows Server includes the container platform that Docker uses, so once a container runtime is installed you can pull and run Windows container images with the normal docker commands. Microsoft's container documentation applies to Windows Server 2025, 2022, 2019 and 2016.

You have three runtime choices, all documented by Microsoft:

One limitation shapes everything else: a Windows Server container host runs Windows containers. If your application ships as a Linux image, run it on a Linux host, or in a Linux virtual machine on the same server with Hyper-V, rather than trying to force it onto the Windows engine.

What Do You Need Before Installing Docker?

You need a Windows Server installation with administrator access, internet access to download the engine and images, and enough disk space for container images, which are large on Windows. Plan for several gigabytes per base image.

• Operating system: Windows Server 2016 or later; Windows Server 2025 or 2022 for current base images and longer support.
• Edition: Standard or Datacenter, Desktop Experience or Server Core.
• Hyper-V role: only needed if you want Hyper-V isolated containers. On a virtual machine, nested virtualisation must be enabled on the host for this.
• PowerShell as administrator: required for the installation script.
• Updates: install the latest cumulative update first, because container images are matched to the host's build.

New to Hyper-V? Our explainer What Is Hyper-V? covers the role and how its virtual machines relate to containers.

How to Install Docker: Windows Server Step by Step

The quickest way to install Docker on Windows Server is Microsoft's install-docker-ce.ps1 script, which turns on the container-related Windows features and installs the Docker engine. The steps below are taken from Microsoft's container setup guide.

1. Sign in as an administrator, right-click Start and open Windows PowerShell (Admin) or Terminal (Admin).
2. Download the script: Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/Windows-Containers/Main/helpful_tools/Install-DockerCE/install-docker-ce.ps1" -o install-docker-ce.ps1
3. Run it: .\install-docker-ce.ps1
4. Allow the server to restart if the script asks; enabling the Containers feature needs a reboot. Run the script again after the restart if it tells you to.
5. Check the engine is running with docker version and docker info.

If your organisation prefers containerd, Microsoft provides a matching install-containerd-runtime.ps1 script that installs containerd, nerdctl and the Windows CNI networking plug-ins. For Mirantis Container Runtime, follow Mirantis's own installer documentation.

How Do You Run Your First Windows Container?

You run your first container by pulling a Microsoft base image whose version matches your server and starting it with docker run. Base images are published on the Microsoft Container Registry (mcr.microsoft.com).

1. Pull the Server Core base image for Windows Server 2025: docker pull mcr.microsoft.com/windows/servercore:ltsc2025
2. Start an interactive container: docker run -it mcr.microsoft.com/windows/servercore:ltsc2025 cmd
3. Inside the container, run hostname or ver to confirm you are in an isolated environment, then type exit.
4. List containers with docker ps -a and remove test containers with docker rm followed by the container ID.

Microsoft publishes several Docker Windows Server base images. Nano Server is the smallest and suits modern .NET apps; Server Core balances size and compatibility and is the usual choice for traditional Windows server apps; the larger Windows Server image adds broader API support and GPU features. On Windows Server 2022 hosts, use the ltsc2022 tags instead.

Process Isolation vs Hyper-V Isolation

Windows containers run in one of two isolation modes, and the choice decides which images will start. Process isolation shares the host's kernel, while Hyper-V isolation gives each container its own lightweight virtual machine and kernel.

The cause-and-effect rule is version matching. Because a process-isolated container uses the host's kernel, Microsoft blocks it from starting when the image's build number differs from the host's, and you get a version incompatibility error. Hyper-V isolation removes that restriction, because the container brings its own kernel, at the cost of more memory and slower start-up.

• Process isolation (the default on Windows Server): fastest and lightest; the image build must match the host.
• Hyper-V isolation: add --isolation=hyperv to docker run; stronger separation and support for older images; requires the Hyper-V role.

Microsoft's container version compatibility matrix lists which host and image combinations work in each mode.

How Are Docker Containers Licensed on Windows Server?

Windows Server Standard allows unlimited Windows containers and up to two Hyper-V isolated containers, while Datacenter allows unlimited containers of both types. Process-isolated containers are covered by the host licence; Hyper-V isolated containers count against the same allowance as virtual machines.

Server licensing is also counted by processor cores, so check how many core licences your hardware needs. Our guide to Hyper-V cost on Windows Server explains how virtual machine rights work alongside containers. For hosts running many isolated containers or VMs, Windows Server 2025 Datacenter removes the limit.

A Common Mistake We See

The most common mistake is pulling an image tag built for a different Windows Server version, for example an ltsc2019 image on a 2025 host, and then seeing the container fail to start. That is the version-matching rule in action. Use the tag that matches your host, or run the container with Hyper-V isolation.

A second mistake is trying to install Docker Desktop on Windows Server because it is the familiar installer. Use the Docker CE script, Mirantis or containerd instead. And because containers follow the host's build, keep the server on a supported release: our Windows Server 2025 licences give you current base images and the longest support window.

Frequently Asked Questions

Is Docker free on Windows Server?

Docker CE, the Moby-based engine installed by Microsoft's script, is open source and free to use. Mirantis Container Runtime is a commercial product with paid support. Docker Desktop has its own subscription terms for larger businesses and is designed for Windows 10 and 11, not Windows Server.

Can I run Linux containers on Windows Server?

Windows Server's container engine runs Windows containers. For Linux containers, the dependable approach is a Linux virtual machine on Hyper-V or a separate Linux host, then run Docker there. This keeps each workload on its native kernel and avoids unsupported configurations in production.

Which version is best for a Docker Windows Server host?

Windows Server 2025 is the best choice for new deployments, because it has the newest base images and the longest support window. Windows Server 2022 remains a solid option if your applications are already built on ltsc2022 images. Older versions limit you to older images.

Do I need the Hyper-V role to run Docker on Windows Server?

No, not for process-isolated containers, which are the default on Windows Server. You only need Hyper-V if you want Hyper-V isolation, for example to run images built for a different Windows version or to add a stronger security boundary between containers.

Can I manage containers from Windows Admin Center?

Yes. Microsoft documents a Windows Admin Center option that prepares a Windows Server machine as a container host and installs Docker in the background. It suits administrators who prefer a browser-based console over PowerShell.

Does Windows Server Standard limit how many containers I can run?

Not for regular Windows containers: Standard allows an unlimited number. The limit applies to Hyper-V isolated containers, where Standard allows up to two. Datacenter has no limit on either type.

Conclusion

Docker on Windows Server is a supported, scriptable setup: install Docker CE with Microsoft's script, pull a base image that matches your host and choose process or Hyper-V isolation deliberately. License the host with the edition that fits your container count. For a new container host, Windows Server 2025 Standard covers unlimited Windows containers at $99.99 at the time of writing.

Useful Links