Public Repository

Last pushed: 13 days ago
Short Description
Windows Server 2016 Server Core base OS image for Windows containers
Full Description

Server Core provides you with a minimal installation of Windows Server 2016 that supports installing only certain server roles.

License: By requesting and using this Container OS Image for Windows containers, you acknowledge, understand, and consent to the following Supplemental License Terms:

Note: Users who may have downloaded an image versioned 10.0.14393.823 should revert to a 10.0.14393.693 based image, we apologize for any confusion this may have caused.

Note: To use the latest base images, be sure to update to the CS release of the Docker Engine and the Docker client

License: By requesting and using this Container OS Image for Windows containers, you acknowledge, understand, and consent to the following Supplemental License Terms:

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:

Docker Pull Command

Comments (38)
6 days ago

@italogarcia There is an open bug for msys2 based program for Windows images:

Spent hours to try to make it work.
My solution: fallback to msysgit based git program available here:

You will have password prompt for https.
set HOME=%USERPROFILE% to get ssh path to work properly.

Hope it will help.

14 days ago

The Crystal Reports runtime fails to install.

I'm starting with microsoft/dotnet-framework:3.5 since it needs the 3.5 framework.

Simply running the installer CRRuntime_64bit_13_0_19.msi a few errors occur towards the end and it aborts the install.

Has anyone been able to install the CR runtime in core?

24 days ago

I created a Docker container using this image and tried to install Git through many ways. All of them installed git under c:\Git. I I'm able to use git with certain limitations which are: I could not manage to authenticate(use private repo) in any way(https and/or ssh), also none of the binaries in C:\Git\usr\bin\ would work at all, they appear to be a bunch of 'nops'. Do you guys have any ideia why this is happening ?

a month ago

If anyone is struggling with adding a secondary disk there is an old school half-way workaround to at least create another 'drive' letter on the container. Create a larger C: and use the subst command. Google psubst for a permanent fix, as this wont survive a reboot but may solve your initial problem without resorting to a mapped network drive. May not be useful but I needed a local E: for my use-case and this was enough to get me going at least.

mkdir c:\drive-e
subst e: c:\drive-e

If anyone can solve this one though let me know. Looks like I simply cannot use the container as it stands.

dism /online /enable-feature /featurename:IIS-NetFxExtensibility /All

Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see

2 months ago

While trying to pull this image, It is showing Repository Not found. Any suggestions??

2 months ago

Does this image support adding new disk drives?
Can I add d: for eg as additional disk to default c:\ that is available?

3 months ago

I have a problem with servercore image, i've added a print-server role via powershell "Add-WindowsFeature Print-Server" but every time i call the Get-Printer cmdlet i obtain an error with the spooler service. In the event log i find some messages of "The Print Spooler service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 5000 milliseconds"

Can anyone help me?
Thank you

3 months ago


Can I add GUI to this image? I tried to add with Install-WindowsFeature but it's not able to mount wim file:

PS C:> dism /Mount-Image /ImageFile:c:\temp\install.wim /Name:"Windows Server 2016 Standard (Desktop Experience)" /MountDir:c:\test

Deployment Image Servicing and Management tool
Version: 10.0.14393.0 be found at C:\Windows\Logs\DISM\dism.log
Error: 0xc1420121

The image could not be mounted because the wimmount.sys driver is not installed on this machine. To fix this error, install the wimmount.sys driver.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:>

3 months ago


docker --version

Docker version 1.12.1, build db440e6


3 months ago

I submitted this DOCKER image with an AMI to Amazon, They flagged a Trojan on it. Win.Trojan.Agent-1819547 . I dont have details what the Trojan does

Vulnerable file(s) detected
Vulnerability found in filepath
Win.Trojan.Agent-1819547: /ProgramData/docker/windowsfilter/fe8f33faede804d39e43d528901162a4e383b272dd4f36926dd518f24dd42679/Files/Windows/servicing/Packages/Microsoft-Windows-ServerCore-Server-Common-Features-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum