Azure Container Apps/Jobs are failing to deploy new images stored in ACR after our images started being published as OCI image indexes rather than direct Docker V2 manifests.

Supriya Gangineni 0 Reputation points
2026-11-02T18:57:20.4333333+00:00

Azure Container Apps/Jobs are failing to deploy new images stored in ACR after our images started being published as OCI image indexes rather than direct Docker V2 manifests.

The affected tag exists in ACR and the OCI index contains a valid linux/amd64 image plus a BuildKit provenance attestation. However, when Container Apps resolves the linux/amd64 child manifest, ACR returns MANIFEST_UNKNOWN for the digest referenced by the index.

This started between our Oct 29 last-known-good build and Nov 2 affected build.

ACR supports OCI images and OCI image indexes: Microsoft ACR supported formats.

Docker documents that BuildKit provenance is attached through an image index: Docker Build Attestations.

We found a similar Azure Container Apps issue involving Buildx provenance and OCI manifest lists: Microsoft Q&A.

--provenance=false works as a potential mitigation, but we are looking for more insights into why Container Apps cannot correctly resolve the linux/amd64 manifest from the OCI index and whether there is a supported fix that allows us to retain provenance.

Azure Container Registry
Azure Container Registry

An Azure service that provides a registry of Docker and Open Container Initiative images.

0 comments No comments

1 answer

Sort by: Newest
  1. Rukshan edirisinghe 2,935 Reputation points
    2026-11-03T04:41:02.1633333+00:00

    Hi @Supriya Gangineni

    One detail in your description changes where to look. MANIFEST_UNKNOWN for the child digest is returned by ACR, not by Container Apps. So before treating this as a Container Apps resolver issue, it's worth proving whether that child manifest really exists in the registry.

    1. Check the child digest directly. Take the linux/amd64 digest from the index and run az acr manifest show-metadata -r <registry> -n <repo>@sha256:<child-digest>. You can also try docker pull <registry>.azurecr.io/<repo>@sha256:<child-digest> from a machine with access.
    2. If the child is missing, the index points to something that isn't there. The usual cause is cleanup. The child manifests of an index have no tag of their own, so an acr purge --untagged task or a custom cleanup script can treat them as untagged. (The built-in retention policy doesn't cover OCI media types, so it's less likely.) Check scheduled Tasks on the registry and any cleanup scripts that ran between Oct 29 and Nov 2. Run purge with --dry-run first to see whether it lists those digests.
    3. If the child is there and pulls fine, the problem is on the Container Apps side. Open a support case with the image digest, the revision name and the timestamps, since only Microsoft can trace the pull inside the managed environment.
    4. To keep provenance in the meantime, build with --provenance=false so the tag points to a plain image manifest. Then attach the provenance separately as an OCI referrer (for example with ORAS), which ACR supports. The image Container Apps pulls stays simple, and the attestation stays linked to it.

    Did anything change in your registry cleanup, or in your build/push tooling, between the Oct 29 and Nov 2 builds?

    If this pins down where the child manifest went, please consider accepting it as the answer. If the digest exists and Container Apps still fails, let me know and I'll be happy to keep helping.

    Reference:

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.