When using sonatype/nexus3:latest or sonatype/nexus3 to pull the latest image (current 3.66.0), docker reports it has the latest image, but the downloaded image is not really the current version.
Indeed, it is the version 3.37.3, which can be confirmed by comparing the image digest with version 3.37.3 on DockerHub.
# URL for version 3.37.3 containing sha256 digest:
https://hub.docker.com/layers/sonatype/nexus3/3.37.3/images/sha256-eff4fb12346ceb5cd424732ee9f2765c0db0f8d5032cdb2f7f7e17acc349f651
# sha256 in URL: eff4fb12346ceb5cd424732ee9f2765c0db0f8d5032cdb2f7f7e17acc349f651
Do you have a workaround you are using at present?
docker pull sonatype/nexus3:latest
latest: Pulling from sonatype/nexus3
Digest: sha256:eff4fb12346ceb5cd424732ee9f2765c0db0f8d5032cdb2f7f7e17acc349f651
Status: Image is up to date for sonatype/nexus3:latest
docker.io/sonatype/nexus3:latest
What feature or behavior is this required for?
The digest from the docker pull command showing that the "latest" image has the same sha256 value
with version 3.37.3.
May be there is a bug in docker that fail to parse the latest version information for the image,
But I never encountered this when working with other images.
How could we solve this issue? (Not knowing is okay!)
Try to pull the image with the latest tag at your environment and check the results.
What problem are you trying to solve?
When using
sonatype/nexus3:latest
orsonatype/nexus3
to pull the latest image (current3.66.0
), docker reports it has the latest image, but the downloaded image is not really the current version. Indeed, it is the version3.37.3
, which can be confirmed by comparing the image digest with version 3.37.3 on DockerHub.Do you have a workaround you are using at present?
What feature or behavior is this required for?
The digest from the
docker pull
command showing that the "latest" image has the same sha256 value with version3.37.3
.May be there is a bug in docker that fail to parse the latest version information for the image, But I never encountered this when working with other images.
How could we solve this issue? (Not knowing is okay!)
Try to pull the image with the
latest
tag at your environment and check the results.