Public Repository

Last pushed: 2 hours ago
Short Description
The official Windows Server Core base image
Full Description

Please note: because Windows does not support running newer versioned containers on older hosts, users MUST be running the latest version of Windows Server 2019 or Windows 10, October 2018 update before pulling the newest Windows Server container images. We disallow uers from pulling a container they could not run. If you try to pull the new container on an older host, you will see:

no matching manifest for unknown in the manifest list entries

In this case, please make sure to update your host.

Supported Windows Server 2016 (Long Term Support Channel) Tags

docker pull

  • ltsc2016, latest
  • 10.0.14393.<Build Number>
  • 10.0.14393.<Build Number>_<Language Code>

Supported Windows Server, version 1709 (Fall Creators Update) Tags

docker pull

  • 1709
  • 1709_KB<Knowledge Base ID>

Supported Windows Server, version 1803 (April 2018 Update) Tags

docker pull

  • 1803
  • 1803_KB<Knowledge Base ID>

Supported Windows Server 2019 (Long Term Support Channel) Tags

docker pull

  • ltsc2019
  • 1809
  • 1809_KB<Knowledge Base ID>

About the image

This is a base image for Windows Server containers. This image carries the Window Servercore base OS image.

How to use this image

As we've been improving the Windows container features, we've had to make some changes that can affect compatibility. Older containers will run the same on newer hosts with Hyper-V isolation, and the same (older) kernel version will still be used. However, if you want to run a container based on a newer Windows build - it can only run on the newer host build.

You can read more on Windows Container Version Compatibility here.

You can simply run the docker image. The default entrypoint is Cmd.exe:

docker run

For support or general questions, please post in our forum.

Please note that we cannot monitor the comment section of each of the Microsoft container images.


Microsoft Corporation (or based on where you live, one of its affiliates) (referenced as “us,” “we,” or “Microsoft”) licenses this Container OS Image supplement to you (“Supplement”). You are licensed to use this Supplement in conjunction with the underlying host operating system software (“Host Software”) solely to assist running the containers feature in the Host Software. The Host Software license terms apply to your use of the Supplement. You may not use it if you do not have a license for the Host Software. You may use this Supplement with each validly licensed copy of the Host Software.

Your use of the Supplement as specified in the preceding paragraph may result in the creation or modification of a container image (“Container Image”) that includes certain Supplement components. For clarity, a Container Image is separate and distinct from a virtual machine or virtual appliance image. Pursuant to these license terms, we grant you a restricted right to redistribute such Supplement components under the following conditions:

(i) you may use the Supplement components only as used in, and as a part of, your Container Image,
(ii) you may use such Supplement components in your Container Image as long as you have significant primary functionality in your Container Image that is materially separate and distinct from the Supplement; and
(iii) you agree to include these license terms (or similar terms required by us or a hoster) with your Container Image to properly license the possible use of the Supplement components by your end-users.
We reserve all other rights not expressly granted herein.

By using this Supplement, you accept these terms. If you do not accept them, do not use this Supplement.

As part of the Supplemental License Terms for this Container OS Image for Windows containers, you are also subject to the underlying Windows Server host software license terms, which are located at

As part of the Supplemental License Terms for this Container OS Image for Windows containers, you are also subject to the underlying Windows Server host software license terms, which are located at

Docker Pull Command