Azure Container Registry Operations: Difference between revisions
Jump to navigation
Jump to search
Line 42: | Line 42: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=Configure AKS Integration with ACR= | =Configure AKS Integration with ACR= | ||
This procedure integrates an ACR instance with an existing AKS cluster. For more details see: {{Internal|Azure_Container_Registry_Concepts#Pulling_Images_to_AKS|Azure Container Registry Concepts | Pulling Images to AKS}} | |||
==CLI== | ==CLI== |
Revision as of 01:41, 13 April 2021
External
Internal
Create
Portal
https://portal.azure.com/ → Create a Resource → Containers → Container Registry
Subscription:
Resource group → Create New
Registry name.
The name may contain only alpha numeric characters and be between 5 and 50 characters.
Name: aksdev.
Will be available as askdevcr.azurecr.io
CLI
Push an Image to Registry
Login. Specify only the registry name when logging in with the Azure CLI. Don't use the login server name, which includes a domain suffix like azurecr.io.
az acr login --name <registry-name>
az acr login --name aksdev
Then push an image available in the local docker cache, tag the image with a new name that contains the image of the login server and push:
docker tag <some-image> <login-server>/<image-name>[:tag]
docker push <login-server>/<image-name>[:tag]
docker tag ovidiufeodorov/httpd:latest aksdev.azurecr.io/http:latest
docker push aksdev.azurecr.io/http:latest
Configure AKS Integration with ACR
This procedure integrates an ACR instance with an existing AKS cluster. For more details see: