You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.NET Core and .NET Framework Windows container images have been updated to use a new tag naming scheme for Windows container images, for both Windows Server Version 1709 and Windows Server 2016.
You will see the following changes in .NET Docker repos:
Notes: The 1709 release is a Semi Annual Channel release, but is missing the sac prefix. Windows Server 2016 Server Core is a Long Term Support Channel release.
Release-specific tags will still be used in Windows repos, which will look like the following examples:
Windows Server 2016 - 10.0.14393.1770
Windows Server 1709 - 1709_KB4043961
The following stable base tags will be used in .NET repos:
Windows Server 2016 Server Core - windowsservercore-ltsc2016
Windows Server 2016 Nano Server - nanoserver-sac2016
Windows Server 1709 Server Core - windowsservercore-1709
Windows Server 1709 Nano Core - nanoserver-1709
The following tags are examples of the new tag scheme:
In cases that an immutable Docker reference is required, you are recommended to use an image digest instead of a tag name. Using an image digest will ensure that docker pull and build always use the same image, even after tags are updated.
The following string is an example of a digest reference:
You can use this string as a parameter to docker pull or docker run. You can also use it with a FROM line to ensure that docker build is consistent, such as with the following.
FROM microsoft/dotnet-framework@sha256:bf8b882633fda16586b69c6f3937f9ccb176ff0c1c77542e175af38d9ee6714e
You can determine an image digest with various Docker commands.
Image digests are displayed with every pull.
C:\>docker pull microsoft/dotnet-framework:4.7.1-windowsservercore-17094.7.1-windowsservercore-1709: Pulling from microsoft/dotnet-frameworkDigest: sha256:bf8b882633fda16586b69c6f3937f9ccb176ff0c1c77542e175af38d9ee6714eStatus: Image is up to date for microsoft/dotnet-framework:4.7.1-windowsservercore-1709
Image digests are displayed for images with the --digests parameter.
$ docker images --digestsREPOSITORY TAG DIGEST IMAGE ID CREATED SIZEmicrosoft/dotnet 2.0-runtime sha256:2e9ae1f83873ffb897f8fb7ada205b67b675a1b2c014d5875a49c050783cc469 c73382e1bbf7 38 hours ago 219MB
Image digests are displayed as part of docker inspect.
We recommend that you use stable tags during development and image digests for production. This approach gives you an opportunity to test any image updates before they affect production apps. .NET images are updated each month with security updates. We recommend that you rebuild your images each month with these updates to ensure that applications are secure. You need to re-pull base images in order to update them. Otherwise, docker build is happy to use stale local copies of base images.
If you are not able to update source Dockerfiles regularly, then it may make more sense to reference stable tags. You still need to rebuild and redeploy your images in order to update your applications in production.
The text was updated successfully, but these errors were encountered:
Windows Docker Tag Scheme Changed
.NET Core and .NET Framework Windows container images have been updated to use a new tag naming scheme for Windows container images, for both Windows Server Version 1709 and Windows Server 2016.
You will see the following changes in .NET Docker repos:
The following tags are examples of the new tag scheme:
This scheme is in use in the following repos:
Discussion
Please share your thoughts on this change and see what others are saying at:
Details
With the release of Windows Server 1709, Windows Server container images adopted stable tags, in addition to the release-specific tags already in use.
The following stable base tags are used in Windows repos, microsoft/nanoserver and microsoft/windowsservercore:
ltsc2016
sac2016
1709
1709
Notes: The 1709 release is a Semi Annual Channel release, but is missing the
sac
prefix. Windows Server 2016 Server Core is a Long Term Support Channel release.Release-specific tags will still be used in Windows repos, which will look like the following examples:
10.0.14393.1770
1709_KB4043961
The following stable base tags will be used in .NET repos:
windowsservercore-ltsc2016
nanoserver-sac2016
windowsservercore-1709
nanoserver-1709
The following tags are examples of the new tag scheme:
This scheme is in use in the following repos:
In cases that an immutable Docker reference is required, you are recommended to use an image digest instead of a tag name. Using an image digest will ensure that docker pull and build always use the same image, even after tags are updated.
The following string is an example of a digest reference:
You can use this string as a parameter to
docker pull
ordocker run
. You can also use it with a FROM line to ensure thatdocker build
is consistent, such as with the following.FROM microsoft/dotnet-framework@sha256:bf8b882633fda16586b69c6f3937f9ccb176ff0c1c77542e175af38d9ee6714e
You can determine an image digest with various Docker commands.
Image digests are displayed with every pull.
Image digests are displayed for images with the
--digests
parameter.Image digests are displayed as part of
docker inspect
.We recommend that you use stable tags during development and image digests for production. This approach gives you an opportunity to test any image updates before they affect production apps. .NET images are updated each month with security updates. We recommend that you rebuild your images each month with these updates to ensure that applications are secure. You need to re-pull base images in order to update them. Otherwise,
docker build
is happy to use stale local copies of base images.If you are not able to update source Dockerfiles regularly, then it may make more sense to reference stable tags. You still need to rebuild and redeploy your images in order to update your applications in production.
The text was updated successfully, but these errors were encountered: