About

This is a Docker on Windows Server 2019 (1809) Vagrant environment for playing with Windows containers.

For Windows Server 2022 (21H2) see the rgl/docker-windows-2022-vagrant repository.

Usage

Install the Base Windows Server 2019 Box.

Install the required plugins:

vagrant plugin install vagrant-reload

Then launch the environment:

vagrant up --provider=virtualbox # or --provider=libvirt

At the end of the provision the examples are run.

The Docker Engine API endpoint is available at http://10.0.0.3:2375.

Graceful Container Shutdown

Windows containers cannot be gracefully shutdown because they are forcefully terminated after a while. Check the moby issue 25982 for progress.

The next table describes whether a docker stop --time 600 <container> will graceful shutdown a container that is running a console, gui, or service app.

base image	app	behavior
mcr.microsoft.com/windows/nanoserver:1809	console	receives the `CTRL_SHUTDOWN_EVENT` notification but is killed after about 5 seconds
mcr.microsoft.com/windows/servercore:1809	console	receives the `CTRL_SHUTDOWN_EVENT` notification but is killed after about 5 seconds
mcr.microsoft.com/windows:1809	console	receives the `CTRL_SHUTDOWN_EVENT` notification but is killed after about 5 seconds
mcr.microsoft.com/windows/nanoserver:1809	service	receives the `SERVICE_CONTROL_PRESHUTDOWN` notification but is killed after about 15 seconds
mcr.microsoft.com/windows/servercore:1809	service	receives the `SERVICE_CONTROL_PRESHUTDOWN` notification but is killed after about 15 seconds
mcr.microsoft.com/windows:1809	service	receives the `SERVICE_CONTROL_PRESHUTDOWN` notification but is killed after about 20 seconds
mcr.microsoft.com/windows/nanoserver:1809	gui	fails to run because there is no GUI support libraries in the base image
mcr.microsoft.com/windows/servercore:1809	gui	does not receive the shutdown messages `WM_QUERYENDSESSION` or `WM_CLOSE`
mcr.microsoft.com/windows:1809	gui	does not receive the shutdown messages `WM_QUERYENDSESSION` or `WM_CLOSE`

NG setting WaitToKillServiceTimeout (e.g. Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control -Name WaitToKillServiceTimeout -Value '450000') does not have any effect on extending the kill service timeout.

NB setting WaitToKillAppTimeout (e.g. New-ItemProperty -Force -Path 'HKU:\.DEFAULT\Control Panel\Desktop' -Name WaitToKillAppTimeout -Value '450000' -PropertyType String) does not have any effect on extending the kill application timeout.

You can launch these example containers from host as:

vagrant execute --sudo -c '/vagrant/ps.ps1 examples/graceful-terminating-console-application/run.ps1'
vagrant execute --sudo -c '/vagrant/ps.ps1 examples/graceful-terminating-windows-service/run.ps1'
vagrant execute --sudo -c '/vagrant/ps.ps1 examples/graceful-terminating-gui-application/run.ps1'

Docker images

This environment builds and uses the following images:

REPOSITORY                                 TAG                     IMAGE ID       CREATED             SIZE
busybox-info                               latest                  2bf5e72aafe4   42 minutes ago      259MB
go-info                                    latest                  644c8601f5e5   42 minutes ago      260MB
csharp-info                                latest                  5f4038c15e58   43 minutes ago      331MB
powershell-info                            latest                  558280d991cc   44 minutes ago      554MB
batch-info                                 latest                  8b94396f136f   45 minutes ago      258MB
busybox                                    latest                  0b904a5f2d77   45 minutes ago      258MB
golang                                     1.19.1                  9dd9a279a9a9   45 minutes ago      788MB
mcr.microsoft.com/powershell               7.2-nanoserver-1809     dc1b9f8b1e6d   8 days ago          530MB
mcr.microsoft.com/dotnet/sdk               6.0-nanoserver-1809     187d361065f2   4 weeks ago         1GB
mcr.microsoft.com/dotnet/runtime           6.0-nanoserver-1809     c5415eb49140   4 weeks ago         331MB
mcr.microsoft.com/windows                  1809                    04a0d4a65546   4 weeks ago         15.8GB
mcr.microsoft.com/windows/servercore       1809                    e795f3f8aa80   4 weeks ago         5.6GB
mcr.microsoft.com/windows/nanoserver       1809                    5fa59fbac916   4 weeks ago         258MB

Troubleshoot

Restart the docker daemon in debug mode and watch the logs:
- set "debug": true inside the $env:ProgramData\docker\config\daemon.json file
- restart docker with Restart-Service docker
- watch the logs with Get-EventLog -LogName Application -Source docker -Newest 50
For more information see the Microsoft Troubleshooting guide and the CleanupContainerHostNetworking page.