A county-clerk filing API builds locally as clerk-api:dev and docker push fails because the tag is not under the registry login server. What publish sequence should the developer follow?
Select an answer to reveal the explanation.
Short Explanation
Docker only pushes tags that already point at the registry’s address. Log in, retag to yourregistry.azurecr.io/repo:tag, then push—like rewriting the shipping label before the parcel leaves the dock.
Full Explanation
ACR expects images tagged with its login server, repository name, and tag (or digest). After az acr login or an equivalent docker login, developers retag the local image to loginServer/repository:tag and push that reference. Pushing an unqualified local name fails because the daemon has no registry destination. Blob Storage and App Service hostnames are not substitutes for the ACR publish path.