Deprecating the Distribution of Microsoft Container Images via Docker Hub

Published 05-19-2021 11:48 AM 6,164 Views
Microsoft

Summary

As containers and cloud native workloads continue to grow, ensuring that customers can reliably acquire vendor artifacts becomes crucial. Microsoft is committed to offer its customers reliable and performant experience for pulling Microsoft container images from the Microsoft Container Registry (MCR or mcr.microsoft.com). MCR contains the full catalog of container images produced by Microsoft with their most up-to-date versions and tags. By leveraging Azure’s global footprint, MCR offers public access to Microsoft’s images globally. With that in mind, we are deprecating all /microsoft org container images hosted in Docker Hub repositories on June 30th, 2021.

 

How does this impact you?

If you continue to reference Microsoft container images using repositories in Docker Hub, this will have impact on your development, deployment, and automation scripts.

Examples for such references are: FROM microsoft/* in Dockerfile or docker run microsoft/* in automation scripts. You can leverage https://grep.app/ to discover such references in OSS scripts.

  • Starting June 1st, 2021 pulls of microsoft/ org container images from Docker Hub registry will be throttled according to Docker Terms of Use. This will limit the number of pulls that you are allowed within certain time period.
  • Starting July 1st, 2021 repositories from microsoft/ org on Docker Hub will be removed. At this point development, deployment and automation scripts that still reference microsoft/ org images from Docker Hub registry will fail.

To avoid any impact on your development, deployment or automation scripts, you must update docker pull commands, FROM statements in Dockerfiles, and other references to microsoft/ container images to explicitly reference the mcr.microsoft.com registry.

We understand that certain repositories from microsoft/ org on Docker Hub registry are highly trafficked, and customers relying on them may not be able to complete these changes by June 30th, 2021. We are working to identify those repositories and provide extension for them. A list of such repositories and for how long they will be available will be published on MCR’s GitHub repository by June 1st, 2021.

 

Mapping of Docker Hub repositories to MCR repositories

Mapping between the repository names on Docker Hub and MCR can be found on MCR's GitHub repository.

 

Guidance for Consuming Public Container Images

Having a controlled workflow for consumption of public content like container images from Docker Hub and MCR is a key for building a secured and reliable software supply chain. Please see the Open Container Initiative’s Consuming Public Content for general guidance and Azure’s guidance for consuming public content.

 

Background

Back in 2018, we announced the transition of Microsoft container images hosting to MCR with syndication to Docker Hub, which laid the ground for worldwide distribution of Microsoft container images. Last year Docker announced an update of their terms of use and plans for image retention – both changes impacting pulls of container images from Docker Hub. Microsoft and Docker have worked closely to provide smooth transition for customers who need to pull /microsoft org container images. Docker Hub pages were updated to reflect the new pull location, mcr.microsoft.com, and are continuously updated with information how to pull up-to-date tags from MCR. We will continue this collaboration to provide an easy and frictionless discoverability mechanism for Microsoft container images through Docker Hub.

 

How to get additional help?

We understand that there may be unanswered questions. You can get additional help by submitting an issue on GitHub or sending an email to mcrfeedback@microsoft.com.

1 Comment

Thank you @toddysm for sharing with the Community :stareyes:

%3CLINGO-SUB%20id%3D%22lingo-sub-2366861%22%20slang%3D%22en-US%22%3EDeprecating%20the%20Distribution%20of%20Microsoft%20Container%20Images%20via%20Docker%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2366861%22%20slang%3D%22en-US%22%3E%3CH2%20id%3D%22toc-hId--465890189%22%20id%3D%22toc-hId--465890193%22%20id%3D%22toc-hId--465976654%22%3ESummary%3C%2FH2%3E%0A%3CP%3EAs%20containers%20and%20cloud%20native%20workloads%20continue%20to%20grow%2C%20ensuring%20that%20customers%20can%20reliably%20acquire%20vendor%20artifacts%20becomes%20crucial.%20Microsoft%20is%20committed%20to%20offer%20its%20customers%20reliable%20and%20performant%20experience%20for%20pulling%20Microsoft%20container%20images%20from%20the%20Microsoft%20Container%20Registry%20(MCR%20or%20mcr.microsoft.com).%20MCR%20contains%20the%20full%20catalog%20of%20container%20images%20produced%20by%20Microsoft%20with%20their%20most%20up-to-date%20versions%20and%20tags.%20By%20leveraging%20Azure%E2%80%99s%20global%20footprint%2C%20MCR%20offers%20public%20access%20to%20Microsoft%E2%80%99s%20images%20globally.%20With%20that%20in%20mind%2C%20we%20are%20deprecating%20all%20%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2Fpublishers%2Fmicrosoftowner%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%2Fmicrosoft%3C%2FA%3E%20org%20container%20images%20hosted%20in%20Docker%20Hub%20repositories%20on%20June%2030%3CSUP%3Eth%3C%2FSUP%3E%2C%202021.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-2021622644%22%20id%3D%22toc-hId-2021622640%22%20id%3D%22toc-hId-2021536179%22%3EHow%20does%20this%20impact%20you%3F%3C%2FH2%3E%0A%3CP%3EIf%20you%20continue%20to%20reference%20Microsoft%20container%20images%20using%20repositories%20in%20Docker%20Hub%2C%20this%20will%20have%20impact%20on%20your%20development%2C%20deployment%2C%20and%20automation%20scripts.%3C%2FP%3E%0A%3CP%3EExamples%20for%20such%20references%20are%3A%3CCODE%3EFROM%20microsoft%2F*%3C%2FCODE%3Ein%20Dockerfile%20or%3CCODE%3Edocker%20run%20microsoft%2F*%3C%2FCODE%3Ein%20automation%20scripts.%20You%20can%20leverage%20%3CA%20href%3D%22https%3A%2F%2Fgrep.app%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fgrep.app%2F%3C%2FA%3E%20to%20discover%20such%20references%20in%20OSS%20scripts.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EStarting%20June%201%3CSUP%3Est%3C%2FSUP%3E%2C%202021%20pulls%20of%20%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2Fpublishers%2Fmicrosoftowner%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Emicrosoft%2F%3C%2FA%3E%20org%20container%20images%20from%20Docker%20Hub%20registry%20will%20be%20throttled%20according%20to%20Docker%20Terms%20of%20Use.%20This%20will%20limit%20the%20number%20of%20pulls%20that%20you%20are%20allowed%20within%20certain%20time%20period.%3C%2FLI%3E%0A%3CLI%3EStarting%20July%201%3CSUP%3Est%3C%2FSUP%3E%2C%202021%20repositories%20from%20microsoft%2F%20org%20on%20Docker%20Hub%20will%20be%20removed.%20At%20this%20point%20development%2C%20deployment%20and%20automation%20scripts%20that%20still%20reference%20%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2Fpublishers%2Fmicrosoftowner%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Emicrosoft%2F%3C%2FA%3E%20org%20images%20from%20Docker%20Hub%20registry%20will%20fail.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ETo%20avoid%20any%20impact%20on%20your%20development%2C%20deployment%20or%20automation%20scripts%2C%20you%20must%20update%3CCODE%3Edocker%20pull%3C%2FCODE%3Ecommands%2C%3CCODE%3EFROM%3C%2FCODE%3Estatements%20in%20Dockerfiles%2C%20and%20other%20references%20to%3CCODE%3Emicrosoft%2F%3C%2FCODE%3Econtainer%20images%20to%20explicitly%20reference%20the%3CCODE%3Emcr.microsoft.com%3C%2FCODE%3Eregistry.%3C%2FP%3E%0A%3CP%3EWe%20understand%20that%20certain%20repositories%20from%20%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2Fpublishers%2Fmicrosoftowner%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Emicrosoft%2F%3C%2FA%3E%20org%20on%20Docker%20Hub%20registry%20are%20highly%20trafficked%2C%20and%20customers%20relying%20on%20them%20may%20not%20be%20able%20to%20complete%20these%20changes%20by%20June%2030%3CSUP%3Eth%3C%2FSUP%3E%2C%202021.%20We%20are%20working%20to%20identify%20those%20repositories%20and%20provide%20extension%20for%20them.%20A%20list%20of%20such%20repositories%20and%20for%20how%20long%20they%20will%20be%20available%20will%20be%20published%20on%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcontainerregistry%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMCR%E2%80%99s%20GitHub%20repository%3C%2FA%3E%20by%20June%201%3CSUP%3Est%3C%2FSUP%3E%2C%202021.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-214168181%22%20id%3D%22toc-hId-214168177%22%20id%3D%22toc-hId-214081716%22%3EMapping%20of%20Docker%20Hub%20repositories%20to%20MCR%20repositories%3C%2FH2%3E%0A%3CP%3EMapping%20between%20the%20repository%20names%20on%20Docker%20Hub%20and%20MCR%20can%20be%20found%20on%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcontainerregistry%2Fblob%2Fmaster%2Fdocs%2Fdockerhub-to-mcr-repo-mapping.md%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EMCR's%20GitHub%20repository%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1593286282%22%20id%3D%22toc-hId--1593286286%22%20id%3D%22toc-hId--1593372747%22%3EGuidance%20for%20Consuming%20Public%20Container%20Images%3C%2FH2%3E%0A%3CP%3EHaving%20a%20controlled%20workflow%20for%20consumption%20of%20public%20content%20like%20container%20images%20from%20Docker%20Hub%20and%20MCR%20is%20a%20key%20for%20building%20a%20secured%20and%20reliable%20software%20supply%20chain.%20Please%20see%20the%20%3CA%20href%3D%22https%3A%2F%2Fopencontainers.org%2Fposts%2Fblog%2F2020-10-30-consuming-public-content%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EOpen%20Container%20Initiative%E2%80%99s%20Consuming%20Public%20Content%3C%2FA%3E%20for%20general%20guidance%20and%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fconsuming-public-content%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAzure%E2%80%99s%20guidance%20for%20consuming%20public%20content%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-894226551%22%20id%3D%22toc-hId-894226547%22%20id%3D%22toc-hId-894140086%22%3EBackground%3C%2FH2%3E%0A%3CP%3EBack%20in%202018%2C%20we%20announced%20the%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fmicrosoft-syndicates-container-catalog%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Etransition%20of%20Microsoft%20container%20images%20hosting%20to%20MCR%20with%20syndication%20to%20Docker%20Hub%3C%2FA%3E%2C%20which%20laid%20the%20ground%20for%20worldwide%20distribution%20of%20Microsoft%20container%20images.%20Last%20year%20%3CA%20href%3D%22https%3A%2F%2Fwww.docker.com%2Fblog%2Fscaling-docker-to-serve-millions-more-developers-network-egress%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EDocker%20announced%20an%20update%20of%20their%20terms%20of%20use%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Fwww.docker.com%2Fblog%2Fdocker-hub-image-retention-policy-delayed-and-subscription-updates%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Eplans%20for%20image%20retention%3C%2FA%3E%20%E2%80%93%20both%20changes%20impacting%20pulls%20of%20container%20images%20from%20Docker%20Hub.%20Microsoft%20and%20Docker%20have%20worked%20closely%20to%20provide%20smooth%20transition%20for%20customers%20who%20need%20to%20pull%20%2Fmicrosoft%20org%20container%20images.%20Docker%20Hub%20pages%20were%20updated%20to%20reflect%20the%20new%20pull%20location%2C%20mcr.microsoft.com%2C%20and%20are%20continuously%20updated%20with%20information%20how%20to%20pull%20up-to-date%20tags%20from%20MCR.%20We%20will%20continue%20this%20collaboration%20to%20provide%20an%20easy%20and%20frictionless%20discoverability%20mechanism%20for%20Microsoft%20container%20images%20through%20Docker%20Hub.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--913227912%22%20id%3D%22toc-hId--913227916%22%20id%3D%22toc-hId--913314377%22%3EHow%20to%20get%20additional%20help%3F%3C%2FH2%3E%0A%3CP%3EWe%20understand%20that%20there%20may%20be%20unanswered%20questions.%20You%20can%20get%20additional%20help%20by%20submitting%20an%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcontainerregistry%2Fissues%2Fnew%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eissue%20on%20GitHub%3C%2FA%3E%20or%20sending%20an%20email%20to%20%3CA%20href%3D%22mailto%3Amcrfeedback%40microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Emcrfeedback%40microsoft.com%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2366861%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22microsoft-container-registry.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F281882i5B56A26F1E8BEBE6%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22microsoft-container-registry.png%22%20alt%3D%22microsoft-container-registry.png%22%20%2F%3E%3C%2FSPAN%3EMicrosoft%20is%20deprecating%20%2Fmicrosoft%20org%20container%20images%20hosted%20in%20Docker%20Hub%20repositories%20on%20June%2030%3CSUP%3Eth%3C%2FSUP%3E%2C%202021.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2371104%22%20slang%3D%22en-US%22%3ERe%3A%20Deprecating%20the%20Distribution%20of%20Microsoft%20Container%20Images%20via%20Docker%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2371104%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F931088%22%20target%3D%22_blank%22%3E%40toddysm%3C%2FA%3E%26nbsp%3Bfor%20sharing%20with%20the%20Community%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2F%40A027B0AAF3CA617A1E2E22C4E761B2FE%2Fimages%2Femoticons%2Fstareyes_40x40.gif%22%20alt%3D%22%3Astareyes%3A%22%20title%3D%22%3Astareyes%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎May 19 2021 12:56 PM
Updated by: