Docker different digest when push same images with different tags -


i built 1 docker image 1 tag , tag new tag (both tags include registry url).

i push first tag, second tag, push digest 2 tags different:

16:10:47 + docker build -t 10.88.102.47:8443/my-project/foo:jenkins-305 . ... 16:11:26 + docker tag 10.88.102.47:8443/my-project/foo:jenkins-305 10.88.102.47:8443/my-project/foo:latest  16:11:26 + docker push 10.88.102.47:8443/my-project/foo:jenkins-305 ... 16:11:34 jenkins-280: digest: sha256:22a4cd54bf43f03530c475832ca4432adfcf02c796e9c1cdafea72cf07ce7bf4 size: 3654  16:11:35 + docker push 10.88.102.47:8443/my-project/foo:latest ... 16:11:36 latest: digest: sha256:ccb4e8c41339b1a5d780cc5d28064cabf839657617a9c1e1d14eaee507405b20 size: 3632 

pushing tag jenkins-305 - digest 22a4cd54bf43f03530c475832ca4432adfcf02c796e9c1cdafea72cf07ce7bf4

pushing tag latest - digest ccb4e8c41339b1a5d780cc5d28064cabf839657617a9c1e1d14eaee507405b20

shouldn't 2 digests of 2 tags same image identical?

update

i downloaded both tags on different machines , see tags have same image id (digest?)

10.88.102.47:8443/my-project/foo   jenkins-305      sha256:5537979d74ac00f75b7830c41c27be5f545ec55b0ab12622f9fad2eec8583a6e   21 minutes ago      689.2 mb 10.88.102.47:8443/my-project/foo   latest           sha256:5537979d74ac00f75b7830c41c27be5f545ec55b0ab12622f9fad2eec8583a6e   21 minutes ago      689.2 mb 

but digest different digest provided docker push, why?

the docs on registry report digest contains image manifest, , manifest made of tag amongst other things.


Comments

Popular posts from this blog

sql - invalid in the select list because it is not contained in either an aggregate function -

Angularjs unit testing - ng-disabled not working when adding text to textarea -

How to start daemon on android by adb -