How to Verify If a Binary Exists in a Filestore

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


Artifactory uniquely stores artifacts using checksum-based storage. This means that an uploaded file will, in order:

  • have its SHA-1 checksum calculated
  • be renamed to its checksum
  • be hosted in the filestore in a directory structure made up of the first two characters of the checksum

Thus, a file whose checksum is ac3f5e56… will stored in directory ac, a file whose checksum is dfe12a4b… will be stored in directory df, and so forth. The example below shows the d4 directory, which contains two files whose individual checksums begin with (you guessed it) d4:
 

User-added image

 

Published: July 8, 2019

Last updated: Apr. 23, 2021

Keywords: Docker Pull