I am have created a customized jenkins using centos docker and storing in docker hub.
When latest tag docker build is good, but release-2.0.1 docker build is not good even though code of latest tag and release-2.0.1 is same.
Those 2 images are totally different in size, and they were created over a day apart.
Pull bitroid/centosjenkins:latest
Last login: Fri Feb 15 07:48:58 on ttys000
🐳 gforghetti:[~] $ docker image pull bitroid/centosjenkins:latest
latest: Pulling from bitroid/centosjenkins
a02a4930cb5d: Pull complete
c702ea4a22bc: Pull complete
a811946ee73e: Pull complete
0eed984e619d: Pull complete
edde8a9b47d0: Pull complete
Digest: sha256:18381ee296f250f1658dde62f023428cdadafdb9388df8ea8cfe14a2334150aa
Status: Downloaded newer image for bitroid/centosjenkins:latest
Pull bitroid/centosjenkins:release-2.0.1
Notice it is not the same image as bitroid/centosjenkins:latest because Docker pulled it.
If it was the same image, the Digets (sha’s) would be the same and Docker would have used the image already downloaded.
I agree that build happened on different date, but master source code and v2.0.1 tag code is same.
Docker tag with latest build is good but docker tag with release-2.0.1 is bad even though it complete without any failure.
Can you please check and advice why this difference in build even though dockerfile code is same.
I recommend that you compare the master code branch and the v2.0.1 tag.
If both are the same, then I recommend that you re-build the v2.0.1 docker image.
Then display the size of the v2.0.1 docker image like I did in my previous post.
I suspect that something “happened” during the build or push to Docker Hub the latest time you did this.