yosifkit
commented
1 month ago The reason for the difference is that more generic tags (like node:alpine) are a combination of each arch-specific node:alpine available (see the arch-specific repos listed in the Docker Official Images readme). Each build architecture pushes images to its respective namespace. A separate job periodically combines those architecture-specific images into the image index under library/ on Docker Hub. Because not all architectures build at the same speed (or one could fail indefinitely), it uses whatever is available under the specific tag for the given architecture. What this means is that for a generic tag (node:alpine), it can be a combination of old (like nodejs 21 on alpine) and new (nodejs 22 on alpine) builds. This helps to ensure that architectures don't just randomly disappear on every version update on the less specific tags when some architectures build faster/slower than others (or fail to build at all).
For example:
ppc64le/node:alpineis still the same asppc64le/node:21-alpineppc64le/node:22-alpinecurrently fails to build, soppc64le/node:alpineis not pushed or updated (https://github.com/docker-library/official-images/pull/16714#issuecomment-2096455085)- the resulting
node:alpinehas appc64leentry (with nodejs 21, but the other architectures are nodejs 22) whilenode:22-alpinedoes not have appc64leentry
Semi-related issue: https://github.com/nodejs/docker-node/issues/718
AJGranowski
Environment
Linux 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 GNU/LinuxDocker version 26.0.0, build 2ae903eExpected Behavior
Tags sharing the same bullet on Docker Hub should resolve to the same index digest.
Current Behavior
Alpine tags have different index digests depending on if the Node version is included in the tag.
22-alpine487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede822-alpine3.19487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede822.1-alpine487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede822.1-alpine3.19487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede822.1.0-alpine487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede822.1.0-alpine3.19487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede8alpine916b42f9e83466eb17d60a441a96f5cd57033bbfee6a80eae8e3249f34cf8dbealpine3.19916b42f9e83466eb17d60a441a96f5cd57033bbfee6a80eae8e3249f34cf8dbecurrent-alpine916b42f9e83466eb17d60a441a96f5cd57033bbfee6a80eae8e3249f34cf8dbecurrent-alpine3.19916b42f9e83466eb17d60a441a96f5cd57033bbfee6a80eae8e3249f34cf8dbe22-alpine3.185a4751fb2e95bb0a0ad5ac1f92fd36076c7337b89667e396dbbabf36fa5b1d6f22.1-alpine3.185a4751fb2e95bb0a0ad5ac1f92fd36076c7337b89667e396dbbabf36fa5b1d6f22.1.0-alpine3.185a4751fb2e95bb0a0ad5ac1f92fd36076c7337b89667e396dbbabf36fa5b1d6falpine3.1816045923d173e53160ee2daa7cd980df38e5a567d8bf9aa62620537393c40a0acurrent-alpine3.1816045923d173e53160ee2daa7cd980df38e5a567d8bf9aa62620537393c40a0aThis split doesn't appear in the bookworm tags.
2264c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3d22-bookworm64c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3d22.164c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3d22.1-bookworm64c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3d22.1.064c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3d22.1.0-bookworm64c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3dbookworm64c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3dcurrent64c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3dcurrent-bookworm64c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3dlatest64c46a664eccedec63941dab4027c178a36debe08a232d4f9d7da5aca91cff3d22.1.0-alpineManifest Digestcurrent-alpineManifest Digest321a52b9fccde74c532796f832046124af1dd997a65410d6155accd40fbe6ab8321a52b9fccde74c532796f832046124af1dd997a65410d6155accd40fbe6ab8c17e937e8e79dc0a5630221cfb8bbef536def6ea5b0c6dfc3779c1d41eb2637ac17e937e8e79dc0a5630221cfb8bbef536def6ea5b0c6dfc3779c1d41eb2637a602f019dd6f03eb5e2196972a98b4f7bcda792e44be2f29ddea01e79ceda4c6e602f019dd6f03eb5e2196972a98b4f7bcda792e44be2f29ddea01e79ceda4c6e2e2092b651047bb52aa815beec42d72a07d46f8b13ff45c57195602062e52fa22e2092b651047bb52aa815beec42d72a07d46f8b13ff45c57195602062e52fa26865bbc0e18da7faba554ca807e8bee075995682450a81ac6f2aca7b45a64c586865bbc0e18da7faba554ca807e8bee075995682450a81ac6f2aca7b45a64c58Possible Solution
Rebuild latest Alpine tags?
Steps to Reproduce
SHA's generated by running
Additional Information
I've previously observed
current-alpinematching<current-version>-alpineover a handful of versions, which is why this discrepancy popped out to me.I'm not aware of this breaking anything. It just seemed like an odd thing the team would be interested in being aware of.