Issues with using Azure Container Registry to store images

Azure Container Registry is a managed, dedicated Docker registry service based on the Docker Registry 2.0 specification. You can create and maintain an Azure container registry to store and manage private Docker container images and related artifacts.
Azure Container Registry is similar to Alibaba Cloud's container image service. A private storage server that provides images. For the 12-month trial account, there is 100GB of free storage and the ability to host 10 webhooks.
Relying on Azure's global nodes can make your images accessible and quickly pulled worldwide.
Here's a simple trial of Azure Container Registry.

Create Resources

Find Container Registry in the list of free services and click Create.

In the pop-up creation interface, fill in the resource group, registry name and other information.
Choose a location that is close to you, such as Southeast Asia.
Select Basic for SKU.
Click the Review + Create button.

After verification, click the "Create" button.

After a few seconds of waiting, our resources are created. Click "Go to Resource" to view the summary information of Azure Container Registry.
The more important one is the one in the upper right corner, login server: minjiezhou.azure.io. It will be used in the following operations.

Upload local image

The following demonstrates how to upload an image to a registry using the Azure CLI command line.

az acr login --name minjiezhou

Log in to Azure Container Registry using the az acr login command.

Please install Azure CLI first.

docker images 

REPOSITORY TAG IMAGE ID CREATED SIZE
mcr.microsoft.com/dotnet/sdk 3.1 b4f189e5f593 3 weeks ago 710MB
mcr.microsoft.com/dotnet/runtime 3.1 e77a510a55f6 3 weeks ago 190MB
kklldog/agile_config test 68288d3f5669 4 weeks ago 281MB
kklldog/agile_config latest 6b2b834fa8d4 5 months ago 281MB

After logging in successfully, let's list the local images first. If there is no local image, go to dockerhub and pull one down first.

docker tag kklldog/agile_config minjiezhou.azurecr.io/agile_config:v1

Let's demonstrate pushing the agile_config image to the container registry.
Use the docker tag command to rename the image. The renamed format is <login server>/agile_config:v1

docker push minjiezhou.azurecr.io/agile_config:v1

The push refers to repository [minjiezhou.azurecr.io/agile_config]
f3f098bf4d75: Pushed
3635892d0647: Pushed
d3d8723bb140: Pushed
bbd61b971886: Pushed
dc4a66fc412f: Pushed
b22af9287e60: Pushed
f5600c6330da: Pushed
v1: digest: sha256:15113de4c788ac61aecdb3a676beaff18f09dd8f786b012e5f14274f295e7dc7 size: 1793

Use the docker push command to start pushing. Wait for the command to complete and then go to the portal to view it.

Click the "Repository" menu and you can see that our agile_config image already exists.

docker rmi minjiezhou.azurecr.io/agile_config:v1

To test pulling the image, we first use the docker rmi command to delete the local image.

docker pull minjiezhou.azurecr.io/agile_config:v1

v1: Pulling from agile_config
Digest: sha256:15113de4c788ac61aecdb3a676beaff18f09dd8f786b012e5f14274f295e7dc7
Status: Downloaded newer image for minjiezhou.azurecr.io/agile_config:v1
minjiezhou.azurecr.io/agile_config:v1

Pull our agile_config image from the Azure Container Registry service using the docker pull command.

Summarize

Through the above simple steps, we demonstrated how to open the Azure Container Registry service through the portal. And how to upload and download docker images through Azure CLI commands. With just a few simple steps, we now have a container registry service that can be easily accessed worldwide.

This is the end of this article about using Azure Container Registry to store images. For more information about Azure Container Registry to store images, please search 123WORDPRESS.COM's previous articles or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future!