[RTFACT-18510] Cached Docker images have different checksums compared with upstream Created: 13/Feb/19  Updated: 28/Feb/19  Resolved: 28/Feb/19

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Docker
Affects Version/s: 5.9.1
Fix Version/s: 6.5.9

Type: Bug Priority: Normal
Reporter: Patrick Russell Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None

Attachments: PNG File Screen Shot 2019-02-13 at 8.24.13 AM.png    


Symptoms: Doing a "docker pull" on the same image through Artifactory has a different checksum.


Steps to reproduce:

  1. Download a Docker image from Docker hub:

patrickr-mac:Downloads patrickr$ docker pull busybox

Using default tag: latest

latest: Pulling from library/busybox

Digest: sha256:7964ad52e396a6e045c39b5a44438424ac52e12e4d5a25d94895f2058cb863a0

Status: Downloaded newer image for busybox:latest

  1. Download the same image through Artifactory:

docker pull artifactory.com/busybox

Using default tag: latest

latest: Pulling from busybox

57c14dd66db0: Pull complete

Digest: sha256:bbb143159af9eabdf45511fd5aab4fd2475d4c0e7fd4a5e154b98e838488e510

Status: Downloaded newer image for mill.jfrog.team:12213/busybox:latest


These images are the same in a "docker inspect":

docker images
jenkinsci/blueocean latest d4bda3da58c2 3 weeks ago 469MB
busybox latest 3a093384ac30 6 weeks ago 1.2MB
artifactory.com/busybox latest 3a093384ac30 6 weeks ago 1.2MB

 This makes using the checksum of Docker images impossible without first pulling the image through Artifactory. 

Comment by Patrick Russell [ 28/Feb/19 ]

Can't reproduce the issue after upgrading.

Generated at Fri Jun 05 21:38:01 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.