Microsoft is committed to making Azure Container Registry (ACR) best-in-class for the storage and distribution of container images. Following this commitment, we’re excited to announce the public preview of Caching for ACR. Once configured, Caching for ACR allows you to cache container images from Docker Hub and Microsoft Artifact Registry in your own ACR instance. This helps you continue using the best in public content and add the speed and reliability of using it from your own networks.
Why Caching for ACR?
Caching for ACR is a new feature added to Azure Container Registry (ACR) currently in preview that allows users to cache container images from Microsoft Artifact Registry and Docker Hub.
Caching container images have three main benefits:
High-speed and reliable pull operations: Faster pulls of container images are achievable by caching the container images in ACR. Since Microsoft manages the Azure network, pull operations are faster, more reliable, and provide Geo-Replication and Availability Zone support to the customers.
Private Network Support: Cached registries are available on private networks. Users can close their firewall to meet compliance standards.
Ensuring upstream content is delivered: All registries, especially public ones like Docker Hub and others, have anonymous pull limits in order to ensure they can provide services to everyone. Caching for ACR allows users to pull images from the local ACR–not the upstream registry.
The Public Preview for Caching for ACR is currently only available in the Azure Portal. The CLI version of Caching for ACR will be available in March of 2023. Caching for ACR supports both authenticated and unauthenticated pulls. If you’d like to try out Caching for ACR, please visit our documents page here.
We’d encourage you to read the document about managing public content here.