Action recommended: Review how you pull container images from Docker Hub

[skhilliard]

Regarding this notification: Review your environments that may be affected by Docker Hub rate limiting before 30 June 2022

Does this apply to Azure DevOp builds also? For example, we have this build step set up...

...the referenced dockerfile has the following...

[SteveLasker]

Hi folks, If your build was from a dedicated agent pool, running on Azure, this applies to you. Microsoft had partnered with Docker to give time for people to transition to authenticated accounts or consume the images they depend upon into environments you manage. This "safety net" will end June 30, 2022. We wanted to provide time for users to either authenticate with docker hub, and/or promote the content they depend upon.

See

• Best Practices for Consuming Public Content
• Azure specific guidance

We are working on an ACR cache feature that will ease this, however, we do not have any additional announcements to make at this point.

[Korijn]

Question: does this affect AKS deployments? As in, will creation of a new AKS cluster cause many Docker Hub pulls? Should I be worried that AKS cluster creation will fail?

[palma21]

No, AKS doesn't use docker hub at all. Just MCR and internal mirrors.

[skhilliard]

Assuming that we have a Docker Hub account, is there some way to use a personal access token in the docker Dev Ops task (as shown above) to use that so that the FROM node:14-slim pull won't be anonymous? Or is the only way to get around this to pull that image to an Azure Container registry?

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[SteveLasker]

Please see: http://aka.ms/acr/cache #close