Managing Container Repositories in Azure Container Registry Tutorial


Azure Container Registry (ACR) is a fully managed container registry service provided by Azure. It allows you to store, manage, and organize Docker container images. In this tutorial, you will learn how to effectively manage container repositories in ACR to ensure efficient organization and maintenance of your Docker images.

Step 1: Create a Container Repository

The first step in managing container repositories in ACR is to create a repository to store your Docker images. You can create a repository using the Azure portal or by using Azure CLI with the following command:

az acr repository create --name --repository

Replace with the name of your Azure Container Registry and with the desired name for your container repository. This command creates a new repository within the specified ACR.

Step 2: Push Docker Images to a Repository

Once you have created a repository, you can push Docker images to it using the Docker CLI. First, tag your local image with the ACR login server address and repository name:

docker tag

Replace with the name of your local Docker image, with the name of your Azure Container Registry, with the name of the repository you created, and with a version or tag for the image. After tagging the image, push it to the repository with the following command:

docker push

This command uploads the Docker image to the specified repository within ACR.

Step 3: Manage Repositories

ACR provides various management capabilities for container repositories. You can use the Azure portal or Azure CLI to perform tasks such as listing repositories, deleting repositories, configuring repository access control, and managing repository webhooks. Here are a few examples of commonly used commands:

  • List all repositories in ACR:
  • az acr repository list --name
  • Delete a repository:
  • az acr repository delete --name --repository
  • Configure repository access control:
  • az acr repository update --name --repository --default-action

Common Mistakes to Avoid

  • Creating repositories with inconsistent naming conventions, leading to confusion and difficulty in managing and organizing images.
  • Forgetting to tag images correctly with the repository name and version, causing issues when pushing and retrieving specific images.
  • Not properly configuring repository access control, potentially exposing sensitive images to unauthorized access.

Frequently Asked Questions (FAQs)

  1. Can I have multiple repositories within a single Azure Container Registry?

    Yes, you can create multiple repositories within a single Azure Container Registry to organize and manage your Docker images effectively.

  2. How can I delete a container repository in ACR?

    You can delete a container repository in ACR using the Azure portal or Azure CLI by running the appropriate commands. Note that deleting a repository permanently removes all images and tags within it.

  3. Can I control access to specific repositories in ACR?

    Yes, you can configure repository access control in ACR to control who can push, pull, or delete images from specific repositories. This helps in enforcing access policies and securing your container images.

  4. What are webhooks in ACR repositories?

    Webhooks in ACR repositories are HTTP callbacks that can be configured to trigger events, such as image push or deletion, and notify external systems or services for further actions or integrations.

  5. Can I list the tags for a specific Docker image within a repository?

    Yes, you can use the Azure CLI or ACR REST API to list the tags associated with a specific Docker image within a repository in ACR.


Managing container repositories in Azure Container Registry (ACR) allows you to organize and maintain your Docker images effectively. By creating repositories, pushing images to them, and leveraging the management capabilities provided by ACR, you can streamline your image storage, access control, and overall image management processes. ACR provides a reliable and scalable solution for hosting and managing container images, making it an essential component of Azure Kubernetes Service (AKS) and other container-based deployments.