Docker and Windows Containers: Overview, Architecture, and Usage

Docker, originally built on Linux namespaces and cgroups, has become the default technology for application distribution and cluster deployment. While Docker originated on Linux, it can also be used on Windows through projects like boot2docker and Docker for Windows.

boot2docker creates a lightweight Linux virtual machine on Windows to run Docker Engine, allowing developers to build and test containerized applications. Docker for Windows bundles a full toolchain—including Docker Engine, Docker Machine, and Docker Swarm—inside a Linux VM, but it only supports Linux‑based container images.

Microsoft collaborated with Docker starting in 2014, introducing Windows container support in Windows Server and Windows 10. Windows containers run native Windows binaries, including IIS‑based applications, and are managed via the same Docker CLI commands as Linux containers.

The Windows container architecture mirrors Linux’s, introducing a Host Compute Service (HCS) that abstracts CGroup and Namespace concepts for Windows. HCS provides stable Go and C# APIs used by Docker to orchestrate containers.

Microsoft offers two Windows container base images: Server Core (full Windows Server features, larger size) and Nano Server (minimal, optimized for containers, smaller size). Dockerfiles for Windows use the same syntax as Linux Dockerfiles.

Licensing for Windows containers does not require additional fees beyond the host OS license.

In summary, Docker can run on Windows either by hosting Linux containers in a VM or by using native Windows containers; both approaches enable developers to adopt cloud‑native, containerized workflows across heterogeneous environments.