-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker image digest incorrect at docker hub #338
Comments
@gdams This is a DockerHub only concern or on us? |
What architecture are you pulling? |
Amd64 |
The ID that You can see the ID in the git history of our Other tools can also show you that the ID you get is the image index id: https://explore.ggcr.dev/?image=eclipse-temurin%3A11.0.17_8-jre. The $ docker pull eclipse-temurin:11.0.17_8-jre
11.0.17_8-jre: Pulling from library/eclipse-temurin
6e3729cf69e0: Already exists
96aa423488f0: Pull complete
a149af9550da: Pull complete
e1a0fd4e771c: Pull complete
Digest: sha256:a22c10c5e01a19f85018f5708a1b2a9ac7b20bc93cb85371359db717827e3c87
Status: Downloaded newer image for eclipse-temurin:11.0.17_8-jre
docker.io/library/eclipse-temurin:11.0.17_8-jre |
See also docker/roadmap#262 👀 😭 |
Please provide a brief summary of the bug
I'm using the
eclipse-temurin:11.0.17_8-jre
image for linux/amd64 from docker hub. According to the tags page, https://hub.docker.com/_/eclipse-temurin/tags?page=1&name=11.0.17_8-jre, the digest of that image should beDigest:sha256:772b0000ef09d2099ef07d1df87b12d942248419e79ff46fa739a5feb617e543
. However, the image I pulled hasDigest:sha256:81b132098ddaba7dc53b67e23e83452f458029a8eeafde911a3076f82d22e946
.Please provide steps to reproduce where possible
Just do a
docker pull eclipse-temurin:11.0.17_8-jre
Expected Results
Image digest should match the sha256 on docker hub.
Actual Results
What Java Version are you using?
Not applicable
What is your operating system and platform?
No response
How did you install Java?
No response
Did it work before?
No response
Did you test with other Java versions?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: