Your CI pipeline pushes an image tagged 'v2.1' to ACR. A deployment that references 'myapp:v2.1' by tag pulls a different image than the one just built. What is the most likely explanation?
- A Tags are immutable, so the deployment cached an old digest
- B Another pipeline reassigned the same tag to a different manifest (correct answer)
- C ACR geo-replication has not finished syncing
- D The image was quarantined by policy
Shortcut: Tags in ACR are mutable pointers to a manifest digest. If two pipelines push the same tag, the later push moves the tag. ) or enable tag immutability via a repository lock to prevent this.
Tags in ACR are mutable pointers to a manifest digest. If two pipelines push the same tag, the later push moves the tag. Pin deployments to the digest (myapp@sha256:...) or enable tag immutability via a repository lock to prevent this.