Windows Server 2019 is the next long-term support release of Windows Server, and it's available now! It comes with some very useful improvements to running Docker Windows containers - which Docker Captain Stefan Scherer has already summarized in his blog post What's new for Docker on Windows Server 2019.
You need Windows Server to run "pure" Docker containers, where the container process runs directly on the host OS. You can use the same Docker images, the same Dockerfiles and the same
docker commands on Windows 10, but there's an additional virtualization overhead, so it's good to use a Windows Server VM for test environments.
On Windows 10 Docker Desktop is the easiest way to get started
If you want to check out the newest version of Windows Server and get running Docker containers, here's what you need to do.
Get Windows Server 2019
You can download the ISO to install Windows Server 2019 now, from your Visual Studio subscription if you have one, or a 180-day evaluation version if you don't. VMs with Windows Server 2019 already deployed will be available on Azure shortly.
The installation procedure for 2019 is the same as previous Windows Server versions - boot a VM from the ISO and the setup starts. I prefer the core installation with no GUI:
I installed Server 2019 onto a Hyper-V VM running on my Windows 10 machine, with the VM disks stored on an external SSD drive. The setup finished in a few minutes, and it runs very quickly - even with just 4GB RAM allocated.
You can also upgrade from previous Windows Server versions to 2019 using the ISO.
Connect to the Server
When you RDP into a Windows Server Core machine you just see a command prompt. The first time you connect you'll need to set the password for the default
Administrator account. Then I like to set PowerShell as the default command shell, so whenever you RDP you get into a PowerShell session:
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' -name Shell -Value 'PowerShell.exe -noExit'
Configure Windows Features
To run containers you need to enable the
Containers feature, and for a non-production VM I also disable Windows Defender to stop it burning CPU cycles. You'll need to reboot after these steps:
Install-WindowsFeature -Name Containers Uninstall-WindowsFeature Windows-Defender Restart-Computer -Force
Configure Windows Updates
You'll want to make sure you have the latest updates, but then I disable automatic updates so I only get future updates when I want them. There's no GUI in Windows Server Core, so run
sconfig and then select:
5, to set Windows Updates to manual
7, to enable Remote Desktop Access to the server
6, to download and install all updates
Then you're ready to install Docker.
Install Docker on Window Server 2019
Windows Server licensing includes the licence cost for Docker Enterprise, so you can run the enterprise edition with production support for containers from Microsoft and Docker.
The latest Docker Enterprise engine is version 18.03, which you can explicitly install with PowerShell:
Install-Module -Name DockerMsftProvider -Repository PSGallery -Force Install-Package -Name docker -ProviderName DockerMsftProvider -Force -RequiredVersion 18.03
This sets up Docker as a Windows Service, which you need to start:
Pull the Windows Base Images
Any Docker containers you run on Windows Server 2019 will be based on Windows Server Core or Nano Server. You'll need both those images, and be aware that the base images are now hosted on Microsoft's container registry, MCR:
docker image pull mcr.microsoft.com/windows/servercore:1809 docker image pull mcr.microsoft.com/windows/nanoserver:1809
These images are tiny compared to the Windows Server 2016 versions. Windows Server Core has shrunk from over 10GB to a 1.5GB download, and Nano Server has shrunk from over 1GB to a 90MB download!
[Optional] Pull the .NET Core Images
The .NET Core team released versions of their SDK and runtime images as soon as Windows Server 2019 launched. You can pull those now and start running your .NET Core apps in 2019 (hopefully the .NET Framework SDK, ASP.NET and SQL Server images will be available soon.)
docker image pull microsoft/dotnet:2.1-sdk-nanoserver-1809 docker image pull microsoft/dotnet:2.1-aspnetcore-runtime-nanoserver-1809
The upstream Docker images are still on Docker Hub, only the base Windows 2019 images are on MCR
Try it Out!
I've pushed an updated version of my .NET Core
whoami image, so you can try out ASP.NET Core 2.1 running in Windows Server Core 2019 containers:
docker container run -d -p 8080:80 sixeyed/whoami-dotnet:nanoserver-1809
One of the enhancements for Docker in Windows Server 2019 is that loopback addresses now work, so you can visit this container using
localhost on the server, and using the same published port from an external machine:
And in Swarm Mode...
I'll post a longer explanation of what you can do with Docker in Windows Server 2019 that you couldn't do in Windows Server 2016, but here's just one other thing: Windows Server 2019 now supports ingress networking for Docker swarm mode. That means you can run multiple containers on one server, all listening on the same port, and Docker will load-balance incoming requests between the containers.
I have lots more detail on this in my Pluralsight course Managing Load Balancing and Scale in Docker Swarm Mode Clusters
Switch your server to a single-node swarm:
docker swarm init --advertise-addr 127.0.0.1
Now deploy the
whoami app as a swarm service, with multiple replicas and a published port:
docker service create ` --publish 8070:80 ` --replicas 5 ` sixeyed/whoami-dotnet:nanoserver-1809
Now when you browse to the VM from outside, Docker will load-balance requests across the five containers which are hosting the service:
Windows Server 2019 is an evolution to the container functionality you get with Docker. Windows Server 2016 is still perfectly fine for production, but 2019 brings Windows containers much closer to feature parity with Linux containers, and smooths over some things which are tricky in 2016.
And the next big thing is Windows support in Kubernetes, which is expected to GA before the end of the year :)