You are configuring a deployment pipeline on a non-Azure container runner that needs to push images to an Azure Container Registry (ACR) named registry2026.azurecr.io. The runner does not have the Azure CLI installed. You create a repository-scoped token named pipeline-token that has permissions restricted to the target repository. Which command and credentials should you use to authenticate the container runner with the registry?
- Run `docker login registry2026.azurecr.io` using `pipeline-token` as the username and one of the generated passwords as the password.Cevap
- BRun `docker login registry2026` using `00000000-0000-0000-0000-000000000000` as the username and the token name as the password.
- CRun `az acr login --name registry2026` using the token name as the username and the token value as the password.
- DRun `docker login registry2026.azurecr.io` using the system-assigned managed identity client ID as the username and the token value as the password.
Cevap
Run `docker login registry2026.azurecr.io` using `pipeline-token` as the username and one of the generated passwords as the password.
The correct answer is to run the standard `docker login` command targeting the fully qualified registry name (`registry2026.azurecr.io`) using the token name (`pipeline-token`) as the username and one of the generated secret passwords as the password. This provides secure, scoped access without needing the Azure CLI or broad admin credentials on a non-Azure runner.
Adım Adım Çözüm
Anahtar Kavram
Azure Container Registry repository-scoped token authentication via Docker CLI
Tahmini Süre:1m 30s