Push the container image to Azure Container Registry

4 minutes

In this unit, you use the Azure Container Registry service to push a container image to your Azure container registry. Azure Container Registry enables you to build, store, and manage container images and artifacts in a private registry for all types of container deployments. Use Azure container registries with your existing container development and deployment pipelines.

Note

If your session has idled out or you're doing this step at another point in time or from another CLI, you might have to reinitialize your environment variables and reauthenticate by using the following commands:

Restore the resource-variable values used in setup. Replace <your-subscription-ID> below with the ID of the subscription you used for this module. If sign-in presents a subscription selector, choose that same subscription. Run the authentication commands one at a time. After az account show, confirm that the active subscription matches setup before continuing. If a command fails, stop and resolve the error.

export AZ_RESOURCE_GROUP=java-containerization-demo-rg
export AZ_CONTAINER_REGISTRY=<your-container-registry>
export AZ_KUBERNETES_CLUSTER=java-containerization-demo-aks
export AZ_LOCATION=<your-Azure-region>
export AZ_KUBERNETES_CLUSTER_DNS_PREFIX=<your-unique-DNS-prefix-to-access-your-AKS-cluster>
az login
az account set --subscription "<your-subscription-ID>"
az account show --output table
az acr login --name "$AZ_CONTAINER_REGISTRY"

Push a container image

You can push your newly built container image to your Azure container registry. By doing so, your container image is network close to all of your Azure resources, such as your Azure Kubernetes Service (AKS) cluster. Later, you configure AKS to pull the flightbookingsystemsample image from the registry. To push the container image to your registry, use the following steps:

Use the following command to sign in to Azure Container Registry, if you haven't already:
```
az acr login
```
Inspect the actual local image before tagging or pushing:
```
docker image inspect flightbookingsystemsample:latest \
  --format '{{.Os}}/{{.Architecture}}'
```
For this path, the result must be linux/amd64. If it differs, rebuild and run the image with --platform linux/amd64 as described in the previous unit before continuing. Tagging and pushing preserve the image platform; they don't change its architecture.
Use the following command to tag the previously built container image with your Azure container registry:
```
docker tag flightbookingsystemsample $AZ_CONTAINER_REGISTRY.azurecr.io/flightbookingsystemsample
```
Use the following command to push the container image to your Azure container registry:
```
docker push $AZ_CONTAINER_REGISTRY.azurecr.io/flightbookingsystemsample
```
After the push completes, you can view the Azure container registry image metadata of the newly pushed image by using the following command:
```
az acr repository show \
    --name $AZ_CONTAINER_REGISTRY \
    --image flightbookingsystemsample:latest
```

The following historical metadata is illustrative. Your image digest and timestamps can differ after you build and push the updated image:

{
  "changeableAttributes": {
    "deleteEnabled": true,
    "listEnabled": true,
    "readEnabled": true,
    "writeEnabled": true
  },
  "createdTime": "2024-11-15T12:23:55.5624474Z",
  "digest": "sha256:13851640a3****************************************f7f1e482c6eaa825",
  "lastUpdateTime": "2024-11-15T12:23:55.5624474Z",
  "name": "latest",
  "signed": false
}

Your container image is now located within your Azure container registry, and is ready for deployments by Azure Services such as AKS.

Feedback

Was this page helpful?