Resolution:

ARTIFACTORY: How to debug ‘unknown blob’ when pulling from a local docker repository

AuthorFullName__c
Loren Yeung
articleNumber
000005281
ft:sourceType
Salesforce
FirstPublishedDate
2022-05-22T11:26:02Z
lastModifiedDate
2024-03-10T07:46:49Z
VersionNumber
5
The easiest way to fix this is by putting the layer back into this folder. We can do a checksum search https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API#ArtifactoryRESTAPI-ChecksumSearch
for 1a437e363abfa47bfe4b3f5906b7444d12346102d944ebddd537e47a62fc6f52

Then if found, we can copy it into where it is supposed to be - the folder where the other layers exist. In my example, this would be under docker-local/library/ubuntu/sha256__7b3e30… note that this is not the ‘20.04’ folder. Note that the file name should be in docker layer format (sha256__<sha256 here>), and it has an attached property that is equal to sha256:<sha256 value>.

If it does not exist in your Artifactory, then the image will have to be re-pushed into Artifactory from another source. If it is a public image, this will be as simple as re-caching it via a remote repository, then copying it into your local. Otherwise, you will need to locate the private source of the image and push it back into Artifactory.