JFROG ARTIFACTORY: What to Do When Your Docker Pull Fails with a ‘500 Binary provider has no content Manifest File’ Error

JFROG ARTIFACTORY: What to Do When Your Docker Pull Fails with a ‘500 Binary provider has no content Manifest File’ Error
AuthorFullName__c
Pradnya Shinde
articleNumber
000004430
ft:sourceType
Salesforce
FirstPublishedDate
2019-07-08T22:47:06Z
lastModifiedDate
2021-04-24
VersionNumber
7

If a Docker pull fails and registers a manifest error that reads: 

Unable to create manifest markers for '….':
Binary provider has no content for '….'

check the following:

  1. In your Artifactory 7.x UI, navigate to Administration Module -> Monitoring -> Service Status (in versions 6.x and below, navigate to Admin > Configuration > High Availability) and verify that your IP values have been correctly configured for all of your nodes.
  2. Through the UI verify if the manifest.json file exists for the Docker artifact. If it’s not there, then it’s not available in Artifactory and therefore explains why your Docker pull failed. If the manifest.json file exists, try to download it from the UI.
  3. If you can view the manifest.json file in the UI, get its SHA-1 value by right clicking manifest.json file > General > Checksums. Then:
  • verifying if its binary exists in the binary store (file system).
  • if you have a sharding cluster, confirm that the binary exists in your filestore, as per the redundancy you have set.
  • if the binary is missing from your filestore then it may have been deleted after your upload of that artifact, which means you’ll then want to discover why this deletion from your file system may have occurred and, thereafter, restore it.