Customer has pull replication set from target remote docker repo to source local docker repo. When read users try to pull the image from the remote docker repo(after event pull replication), it fails with the error below, even if the image exists in the remote repo/cache.
2019-01-28 23:50:25,671 [http-nio-8081-exec-3] [ERROR] (o.a.a.d.r.v.DockerV2RemoteRepoHandler:421) - Unable to create manifest markers for 'docker-replication:busybox/2.0.0/manifest.json': 'User testuser is not permitted to deploy 'busybox/2.0.0*/list.manifest.json'* into 'docker-replication-cache:busybox/2.0.0/list.manifest.json'.'
Noticed that while we pull from a remote repo(source), Artifactory tries to create list.manifest.json file, but when we push the same image to local repo, the image does not create list.manifest.json file.
Similarly, after pull replication the target remote repo does not create list.manifest.json file and this might be a reason why docker pull is failing in this use case.
When list.manifest.json is unavailable, Artifactory should ignore and pull the image instead of trying to create list.manifest.json and cache it.
NOTE: Customer have limitation in providing Deploy/Cache privileges to the users.
Users with read permission should be able to pull images which are available in the remote repo/cache without Deploy/cache permissions. Can we add a functionality, if list.manifest.json is unavailable, Artifactory should ignore and pull the image instead of trying to create list.manifest.json and cache it in the remote repo?