Evaluate implications with Cache for Azure Container Registry to mitigate the effects of rate limiting

[emirgens]

Begin managing public content with Cache for Azure Container Registry to mitigate the effects of rate limiting

If you use content in Azure directly from third-party registries, such as Docker Hub, you may be subject to current or upcoming rate limits. To help you mitigate potential breaking changes or service disruptions that rate limiting can cause, we've introduced a new feature called Cache for Azure Container Registry.

This preview feature can be configured to behave as a pull-through cache for user-selected third party images. You may want to use this feature to mitigate the potential effects of rate limiting depending on your circumstances:

• If you use Docker Hub, you may be affected by Docker rate limiting beginning 30 September 2023.
• If you use other third-party registries, you may be affected by rate limiting now.
• If you pull images directly from Azure Container Registry, you won't be affected by rate limiting.
• If you have a Docker subscription and you provide your credentials during an image pull, this change may not affect you. Learn about Docker subscriptions and Enhanced Service Account add-ons to determine whether you're affected.

Recommended action

To mitigate the potential effects of third-party rate limiting, review how you reference containers in your environments and test the Cache for Azure Container Registryfeature. Then, begin managing your public content with Azure Container Registry.
If you use Docker Hub, take these actions by 30 September 2023, when Docker rate limiting may begin to affect you. Or, you may mitigate the effects of rate limiting by purchasing a Docker subscription.

Link to Slack message

From MS documentation:
100 pulls pr 6 hrs pr. IP