microsoft/windows-servercore-iis repository overview

⁠IIS Docker Image

⁠Supported Windows Server 2025 amd64 tags

docker pull mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2025 windowsservercore-ltsc2025, latest (windowsserver/Dockerfile)⁠

⁠Supported Windows Server 2022 amd64 tags

docker pull mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2022 windowsservercore-ltsc2022, latest (windowsserver/Dockerfile)⁠

⁠Supported Windows Server 2019 amd64 tags

docker pull mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2019 windowsservercore-ltsc2019, latest (windowsserver/Dockerfile)⁠

⁠Supported Windows Server 2016 amd64 tags

docker pull mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2016 windowsservercore-ltsc2016, latest (windowsserver/Dockerfile)⁠

⁠About This Image

Internet Information Services (IIS) for Windows® Server is a flexible, secure and manageable Web server for hosting anything on the Web.

⁠How to use this image?

⁠Create a Dockerfile with your website

FROM mcr.microsoft.com/windows/servercore/iis

RUN powershell -NoProfile -Command Remove-Item -Recurse C:\inetpub\wwwroot\*

WORKDIR /inetpub/wwwroot

COPY content/ .

You can then build and run the Docker image:

$ docker build -t iis-site .
$ docker run -d -p 8000:80 --name my-running-site iis-site

You do not need to specify an ENTRYPOINT in your Dockerfile because the microsoft/iis base image already includes an entrypoint application, ServiceMonitor.exe, which monitors the status of the IIS World Wide Web Publishing Service (W3SVC).

Note: The drop location for Service Monitor has changed. It is now available at the https://github.com/microsoft/IIS.ServiceMonitor/releases⁠. The original location, https://dotnetbinaries.blob.core.windows.net/⁠, will be removed on 2025-06-10. See https://github.com/dotnet/announcements/issues/351⁠ for more information.

⁠Verify in the browser

Once the container starts, you'll need to finds its IP address so that you can connect to your running container from a browser. You use the docker inspect command to do that:

docker inspect -f "{{ .NetworkSettings.Networks.nat.IPAddress }}" my-running-site

You will see an output similar to this:

172.28.103.186

You can connect the running container using the IP address and configured port, http://172.28.103.186:8000 in the example shown.

In addition to static content, IIS can run other workloads including but not limited to ASP.NET, ASP.NET Core, NodeJS, PHP, and Apache Tomcat.

For a comprehensive tutorial on running an ASP.NET app in a container, check out the tutorial on the docs site⁠.

⁠Related Repos

• microsoft/aspnet⁠: ASP.NET container image
• microsoft/wcf⁠: WCF container image
• microsoft/iis/insider⁠: Insider version of IIS image based on insider OS with beta features.

⁠Full Tag Listing

⁠Windows Images

⁠Multi-arch Images

You can retrieve a list of all available tags for windows/servercore/iis at https://mcr.microsoft.com/v2/windows/servercore/iis/tags/list⁠

⁠Tag Lifecycle

Each tag will be supported for the lifetime of the OS version referenced by the tag. There are some exceptions:

• Tags containing a timestamp are supported until a newer timestamp is published for the Windows Server version. This typically occurs on a monthly basis on "Patch Tuesday"⁠.

• The multi-arch tags 'latest', and 'windowsservercore' will reference the latest versions of Windows Server Core at the time the image was published.

• The 'windowsservercore-ltsc*' will reference the latest version of Windows Server Core, referenced by the tag, at the time the image was published.

When an OS version reaches End-of-Life (EOL), its tags will no longer be maintained.

Once a tag is no longer maintained, it will be considered unsupported and will no longer be updated. Unsupported tags will remain in the container registry to prevent breaking any references to them.

⁠Examples

• 'latest' and 'windowsservercore' - multi-arch tags will be supported for the lifetime of the versions of Windows Server Core release as long as the latest published version of the image is being used.

• 'windowservercore-ltsc2022' - will be supported for the lifetime of the Windows Server Core LTSC 2022 releases as long as the latest published version of the image is being used.

• '20250408-windowsservercore-ltsc2025' - will be supported only until a newer timestamp is published for the Windows Server Core version.

⁠Feedback

If you have any issues or concerns, reach out to us through a GitHub issue⁠.

⁠License

• Legal Notice: Container License Information⁠

MICROSOFT SOFTWARE SUPPLEMENTAL LICENSE TERMS CONTAINER OS IMAGE
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.

ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS
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 https://www.microsoft.com/en-us/useterms⁠