Once you have the required images locally, you can add new tags to them with docker tag. Or make this more storage-and-time efficient, finding the tags you want for that docker image and executing the pull command to download only them. You can either pull all tags of a given image: docker pull microsoft/ dotnet -a The re-tagging command takes place locally, so before you can do that, you need to pull the required images locally. Or the azure CLI command: az acr login -n ACR_NAME -g RESOURCE_GROUP_NAME -username USER_NAME -password PASSWORD 1. For Azure ACR, you can either use the docker login command: docker login -username USER_NAME -password PASSWORD ACR_ In order to make push images into a registry, you need to authenticate against it. However, below I will just cover the “how to” automate the process of re-tagging public images so you can push them into your internal CR.
#Move to another place how to#
I won’t be focusing on why or how to do any of the above, as it could be quite specific. Generally that would result in “Golden Images” or simply base images that would be white-listed for internal consumption.
In a business, when consuming public docker images, you may want to sanitise them, running some processes before putting them to use.