From bf173136f5c88f046a9a018336b5a86e9098bcdd Mon Sep 17 00:00:00 2001 From: alexbelgium Date: Tue, 21 Jul 2026 20:15:41 +0200 Subject: [PATCH] elasticsearch: build FROM docker.elastic.co instead of Docker Hub mirror The updater tracks elastic/elasticsearch GitHub tags and bumps as soon as a tag appears, but the build pulled `FROM elasticsearch:` (the Docker Hub `library/elasticsearch` mirror), whose arm64/aarch64 tag lags hours behind the release. This broke the aarch64 build right after "updated to 8.19.19" (and would recur on every release): docker.io/library/elasticsearch:8.19.19 had only linux/amd64 at build time, no arm64. Switch to Elastic's own registry, which publishes the multi-arch image atomically with the GitHub tag the updater watches. The image is otherwise identical (same User 1000:0, tini entrypoint, eswrapper cmd), so the entrypoint patch and uid handling are unchanged, and the updater's blanket version sed over the Dockerfile is unaffected. Co-Authored-By: Claude Opus 4.8 --- elasticsearch/Dockerfile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/elasticsearch/Dockerfile b/elasticsearch/Dockerfile index bf2cb19344..ccaee43a08 100644 --- a/elasticsearch/Dockerfile +++ b/elasticsearch/Dockerfile @@ -15,7 +15,11 @@ ################# ARG BUILD_UPSTREAM="8.19.19" -FROM elasticsearch:$BUILD_UPSTREAM +# Pull from Elastic's own registry (multi-arch, published atomically with the +# GitHub release the updater tracks) rather than the Docker Hub "library" +# mirror, whose arm64/aarch64 tag lags hours behind and breaks the aarch64 +# build right after an update (e.g. elasticsearch:8.19.19 arm64 missing). +FROM docker.elastic.co/elasticsearch/elasticsearch:$BUILD_UPSTREAM # The base image ends as USER 1000:0 with a root-owned, read-only (0555) # entrypoint; switch back to root for the remaining build steps (entrypoint