An Azure service that provides a registry of Docker and Open Container Initiative images.
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.
- 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 trydocker pull <registry>.azurecr.io/<repo>@sha256:<child-digest>from a machine with access. - 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 --untaggedtask 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-runfirst to see whether it lists those digests. - 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.
- To keep provenance in the meantime, build with
--provenance=falseso 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: