10.3.3 Azure Container Registry
A focused guide to Azure Container Registry, connecting core concepts with practical Docker and container operations.
Azure Container Registry (ACR) is Microsoft Azure's managed container registry service, providing the same kind of tightly integrated, cloud-native registry experience for Azure-deployed workloads that ECR and Artifact Registry provide for AWS and Google Cloud respectively.
Creating an ACR Instance
A registry instance is created within a specific Azure resource group and region.
az acr create --resource-group myResourceGroup --name myacrregistry --sku Basic
Authenticating With ACR
The Azure CLI provides a direct way to authenticate Docker against a specific ACR instance, integrating with Azure's own credential system.
az acr login --name myacrregistry
This configures Docker to authenticate against this specific registry using the currently active Azure CLI session's credentials.
Pushing an Image to ACR
Once authenticated, pushing follows the standard pattern, using ACR's specific registry hostname.
docker tag myapp:1.0 myacrregistry.azurecr.io/myapp:1.0
docker push myacrregistry.azurecr.io/myapp:1.0
Why ACR Integrates Naturally With Other Azure Services
A service deployed to Azure Kubernetes Service (AKS) or Azure Container Instances, within the same Azure subscription, can pull from ACR using Azure's own identity and access management, without needing a separately managed registry credential.
az aks update -n myAKSCluster -g myResourceGroup --attach-acr myacrregistry
This command explicitly grants an AKS cluster pull access to a specific ACR instance, integrating registry access directly into Azure's existing resource and identity management.
Why Azure Container Registry Matters
For workloads deployed on Azure, ACR provides the same kind of seamless, identity-integrated registry experience available on other major cloud platforms, simplifying authentication and access management for teams operating within the Azure ecosystem.