Issue
When using the same Docker tag for both single-architecture and multi-architecture image pushes, Artifactory retains both the image manifest (manifest.json) and the manifest list (list.manifest.json) under the same tag.
As a result, subsequent docker pull operations continue to resolve to the multi-architecture manifest list, and download statistics are recorded only for list.manifest.json. This behavior can be unexpected for users who anticipate that pushing a newer single-architecture image with the same tag will overwrite the existing multi-architecture image, leaving only the latest single-architecture manifest associated with that tag.
Instead, the previously published multi-architecture manifest remains available and continues to be served during image pulls.
Solution
The multiple manifests per tag behavior is caused by Artifactory’s default protection mechanism, which is designed to prevent accidental pushes of single-architecture images from overwriting or disrupting existing multi-architecture image manifests associated with the same tag.
To allow newer single-architecture pushes to fully overwrite and replace multi-architecture entries, it is possible to enforce the Strict Tag Overwrite feature introduced in Artifactory 7.144.2.
To do this, navigate to Administration → Artifactory Settings → Packages Settings → Docker, OCI, HelmOCI and check Enforce Strict Tag Overwrite.
When this option is enabled, users must have Delete/Overwrite permissions to push an image using an existing name and tag. This ensures that multiple manifest types cannot coexist under the same tag.