avm/hassio-addons
1
0
Fork 0
mirror of https://github.com/alexbelgium/hassio-addons.git synced 2026-08-29 16:23:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

elasticsearch: build FROM docker.elastic.co instead of Docker Hub mirror

Browse Source 
The updater tracks elastic/elasticsearch GitHub tags and bumps as soon as a
tag appears, but the build pulled `FROM elasticsearch:<v>` (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 <noreply@anthropic.com>
This commit is contained in:
alexbelgium
2026-07-21 20:15:41 +02:00
parent 57366eeacc
commit bf173136f5
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
elasticsearch/Dockerfile
View File

@@ -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