Unable to pull images from Azure Container Registry

Question

When pulling images from our Azure Container Registry, we are receiving an error on some images. It seems to be that OCI images cannot be pulled, but Docker images can be pulled, both using the same Azure authentication. There were no issues with this until today and no changes have been made to our ACR, and the image that cannot be pulled has not been changed since October 2024.

Below is the result of pulling a docker image

docker pull myacr.azurecr.io/myworkingapp:latest
latest: Pulling from sdsposweb
1f02dbab0012: Already exists
0dd874da2557: Already exists
4854e2ceb538: Already exists
d6ba0b2a5a94: Already exists
1f1419a605e0: Already exists
4fb75ee0fdd4: Already exists
018d46d71660: Pull complete
40e9771587e3: Pull complete
e6c5b36f6df5: Pull complete
a37020e19a49: Pull complete
d0707423568b: Pull complete
4f4fb700ef54: Pull complete
bca30395f407: Pull complete
242a08742c87: Pull complete
3e2d3fa7a434: Pull complete
50382b171d9b: Pull complete
f9459ba5ba2c: Pull complete
d5ada15aa61b: Pull complete
Digest: sha256:a7303ebd7954c60bac0496178fda91126aae8c035b51810fa9a9a83bb5511595
Status: Downloaded newer image for myacr.azurecr.io/myworkingapp:latest
myacr.azurecr.io/myworkingapp:latest

Compare to the below run just before pulling an ACR image

docker pull myacr.azurecr.io/sql2019-basedata:build_smoketest_central_wa_alpha-5632-v1
build_smoketest_central_wa_alpha-5632-v1: Pulling from sql2019-basedata
manifest for myacr.azurecr.io/sql2019-basedata:build_smoketest_central_wa_alpha-5632-v1 not found: manifest unknown: manifest sha256:570f72a14ed9c949ba91be0112cb02652a6b254b74eb12ed6d27828912add4af is not found

Answer 1

Hi Mike Navin,

Based on your description, you're experiencing an issue where Docker images can be pulled from your Azure Container Registry, but OCI images fail with a "manifest not found" error.

ACR supports both OCI and Docker images, but there might be a bug or configuration issue. OCI images have a different manifest format compared to Docker images. "Manifest not found" error can occur even when the image exists in the registry and is often related to how the image manifests are stored and referenced. Make sure that the tag exists within the associated repository and registry.

Please check this document with detailed information: "Manifest unknown: manifest tagged by '<tag>' is not found" error

List the manifests for a repository, which can help you verify whether the problematic image manifest actually exists. Please check this document for detailed information: Manage OCI Artifacts

If you have any further queries, let me know. If the information is helpful, please click on Upvote on it.