Home
%3CLINGO-SUB%20id%3D%22lingo-sub-382435%22%20slang%3D%22en-US%22%3EUpdates%20to%20Our%20Container%20Tagging%20Format%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382435%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Jan%2026%2C%202019%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20We're%20introducing%26nbsp%3Bseveral%20minor%20changes%20to%20the%20tagging%20format%20of%20Windows%20containers.%20These%20changes%20will%20begin%20taking%20take%20effect%20next%20Patch%20Tuesday%2C%20February%2012%2C%202019.%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1731669112%22%3EBuild%20Number%20Tags%3C%2FH2%3E%3CBR%20%2F%3E%20We%E2%80%99re%20re-introducing%20a%20build%20tag%20across%20all%20Windows%20base%20images.%20This%20will%20complement%20the%20existing%20KB-formatted%20tag%20and%20release%20channel%20tags.%20Here%E2%80%99s%20an%20example%3A%20%3CBR%20%2F%3E%20%23The%20equivalent%20build%20number%20for%20the%20latest%20KB4480116%2C%20which%20went%20live%20for%20January%20Patch%20Tuesday%3A%20%3CBR%20%2F%3E%20docker%20pull%20mcr.microsoft.com%2Fwindows%2Fservercore%3A10.0.17763.253%20%3CBR%20%2F%3E%20We%20released%20Windows%20Server%202016%20container%20images%20with%20two%20tags%20forms.%20The%20first%20was%20the%20release%20channels%2C%20ltsc2016%20and%20sac2016.%20The%20second%20was%20a%20build%20number.%20With%20the%20release%20of%20Windows%20Server%2C%20version%201709%2C%20we%20moved%20away%20from%20the%20build%20number%20to%20a%20Knowledge%20Base%20number%20system.%20That%20way%2C%20users%20could%20search%20the%20KB%20number%20and%20find%20the%20associated%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4480116%2Fwindows-10-update-kb4480116%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20support%20article%20%3C%2FA%3E%20to%20understand%20what%20patches%20were%20in%20the%20image.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Feedback%20from%20users%20indicated%20that%20the%20KB%20tag%20alone%20was%20not%20clear%20enough%20in%20communicating%20which%20image%20was%20in%20fact%20newer%20or%20whether%20the%20container%20image%20was%20an%20exact%20match%20to%20their%20host%20OS%20version.%20We%20believe%20users%20will%20have%20an%20easier%20time%20distinguishing%20these%20things%20with%20the%20reintroduction%20of%20the%20build%20tag.%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--820487849%22%3EConsistent%20Tags%20Across%20all%20Microsoft%20Repos%3C%2FH2%3E%3CBR%20%2F%3E%20To%20have%20consistency%20across%20all%20Microsoft%20container%20repos%2C%20going%20forward%2C%20all%20container%20image%20tags%20that%20were%20previously%20published%20with%20an%20underscore%20will%20now%20be%20published%20with%20a%20hyphen.%20Example%3A%20%3CBR%20%2F%3E%20%23This%20is%20how%20it%20was%20before%3A%20%3CBR%20%2F%3E%20docker%20pull%20mcr.microsoft.com%2Fwindows%2Fservercore%3A1809_KB4480116_amd64%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%23This%20is%20how%20it%20will%20be%20going%20forward%3A%20%3CBR%20%2F%3E%20docker%20pull%20mcr.microsoft.com%2Fwindows%2Fservercore%3A1809-KB4480116-amd64%20%3CBR%20%2F%3E%20This%20change%20will%20affect%20all%20image%20tags%20published%20going%20forward.%20Old%20tags%20that%20used%20an%20underscore%20will%20continue%20to%20exist.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We%E2%80%99re%20also%20updating%20our%20arch-specific%20ARM%20images%20to%20align%20with%20the%20rest%20of%20the%20Docker%20community%2C%20changing%20from%20a%20tag%20of%20%E2%80%98arm%E2%80%99%20for%2032-bit%20arm%20to%20%E2%80%98arm32v7%E2%80%99.%20As%20an%20example%20of%20this%20change%3A%20%3CBR%20%2F%3E%20%23This%20is%20how%20it%20was%20before%3A%20%3CBR%20%2F%3E%20docker%20pull%20mcr.microsoft.com%2Fwindows%2Fnanoserver%3A1809_arm%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%23This%20is%20how%20it%20will%20be%20going%20forward%3A%20%3CBR%20%2F%3E%20docker%20pull%20mcr.microsoft.com%2Fwindows%2Fnanoserver%3A1809-arm32v7%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-922322486%22%3EContainer%20Repo%20Structure%3C%2FH2%3E%3CBR%20%2F%3E%20In%20related%20news%2C%20Docker%20%3CA%20href%3D%22https%3A%2F%2Fblog.docker.com%2F2018%2F12%2Fthe-new-docker-hub%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20introduced%20%3C%2FA%3E%20changes%20to%20Docker%20Hub.%20Docker%20Hub%20is%20the%20home%20to%20our%20new%20repository%20structure.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F97128i738F75F62B42B229%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20new%20structure%20allows%20us%20to%20have%20a%20repository%20family%20page%E2%80%94the%20%E2%80%9CWindows%20base%20OS%20Images%E2%80%9D%E2%80%94displayed%20above.%20From%20there%2C%20the%20family%20page%20links%20to%20the%20individual%20repos%20for%20all%20Windows%20container%20base%20images%20and%20points%20users%20to%20related%20repos.%20You%20can%20read%20more%20in%20a%20%3CA%20href%3D%22https%3A%2F%2Fcloudblogs.microsoft.com%2Fopensource%2F2019%2F01%2F17%2Fimproved-discovery-experience-microsoft-containers-docker-hub%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20blog%20post%20%3C%2FA%3E%20from%20Rohit%20Tatachar%2C%20PM%20for%20Container%20Registry.%20%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1629834475%22%3EConclusion%3C%2FH2%3E%3CBR%20%2F%3E%20For%20more%20information%2C%20please%20visit%20our%20container%20docs%20at%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fwindowscontainers%2Fdeploy-containers%2Fversion-compatibility%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20aka.ms%2Fcontainers%20%3C%2FA%3E%20.%20Let%20us%20know%20your%20thoughts%20about%20the%20new%20repo%20structure%20in%20the%20comments%20below!%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-382435%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Jan%2026%2C%202019%20We're%20introducing%26nbsp%3Bseveral%20minor%20changes%20to%20the%20tagging%20format%20of%20Windows%20containers.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-382435%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EContainers%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Edocker%20hub%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Etags%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Not applicable
First published on TECHNET on Jan 26, 2019
We're introducing several minor changes to the tagging format of Windows containers. These changes will begin taking take effect next Patch Tuesday, February 12, 2019.

Build Number Tags


We’re re-introducing a build tag across all Windows base images. This will complement the existing KB-formatted tag and release channel tags. Here’s an example:
#The equivalent build number for the latest KB4480116, which went live for January Patch Tuesday:
docker pull mcr.microsoft.com/windows/servercore:10.0.17763.253
We released Windows Server 2016 container images with two tags forms. The first was the release channels, ltsc2016 and sac2016. The second was a build number. With the release of Windows Server, version 1709, we moved away from the build number to a Knowledge Base number system. That way, users could search the KB number and find the associated support article to understand what patches were in the image.

Feedback from users indicated that the KB tag alone was not clear enough in communicating which image was in fact newer or whether the container image was an exact match to their host OS version. We believe users will have an easier time distinguishing these things with the reintroduction of the build tag.

Consistent Tags Across all Microsoft Repos


To have consistency across all Microsoft container repos, going forward, all container image tags that were previously published with an underscore will now be published with a hyphen. Example:
#This is how it was before:
docker pull mcr.microsoft.com/windows/servercore:1809_KB4480116_amd64

#This is how it will be going forward:
docker pull mcr.microsoft.com/windows/servercore:1809-KB4480116-amd64
This change will affect all image tags published going forward. Old tags that used an underscore will continue to exist.

We’re also updating our arch-specific ARM images to align with the rest of the Docker community, changing from a tag of ‘arm’ for 32-bit arm to ‘arm32v7’. As an example of this change:
#This is how it was before:
docker pull mcr.microsoft.com/windows/nanoserver:1809_arm

#This is how it will be going forward:
docker pull mcr.microsoft.com/windows/nanoserver:1809-arm32v7

Container Repo Structure


In related news, Docker introduced changes to Docker Hub. Docker Hub is the home to our new repository structure.



The new structure allows us to have a repository family page—the “Windows base OS Images”—displayed above. From there, the family page links to the individual repos for all Windows container base images and points users to related repos. You can read more in a blog post from Rohit Tatachar, PM for Container Registry.

Conclusion


For more information, please visit our container docs at aka.ms/containers . Let us know your thoughts about the new repo structure in the comments below!