mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-08-17 02:17:20 +02:00
Reported: on upgrade from an existing 7.17.9 install, the add-on failed to start with "mv: cannot move '/data/config' to '/data/config.bak-7.17.9': Permission denied". Root cause: a previous fix in this same release restored `USER 1000:0` at the end of the Dockerfile to match the upstream base image's own final USER directive. But the upstream 8.19 entrypoint no longer drops privileges itself (confirmed: it execs elasticsearch directly, no gosu/chroot dance), and existing installs have /data owned by root (7.17.9's default image variant runs fully as root). A non-root container can never chown or move that data. Revert to root at runtime, matching how this add-on always ran and matching its own AppArmor profile (chown, setuid, setgid, sys_chroot, mount capabilities — all meaningless for a non-root process anyway). Root stays required for the build-time entrypoint patch too, unchanged from the prior fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
3.0 KiB
3.0 KiB
8.19.18 (2026-07-14)
- Upgrade to Elasticsearch 8.19.18 (#2849). Note: despite the previous add-on version reading
8.14.3, the shipped image was still Elasticsearch 7.17.9 — the Dockerfile upstream version was never bumped. This release actually delivers 8.x, making the add-on compatible with thehomeassistant-elasticsearchintegration (requires 8.14+). - Automatic data migration: existing 7.17 data is upgraded in place by Elasticsearch on first start (one-way; can take a while on large datasets). A migration guard aborts with a clear message on unsupported paths (downgrades, or data more than one major version old). Take a Home Assistant backup before updating.
- The previous bundled config directory is archived to
/data/config.bak-<old-version>during major upgrades; re-apply custom settings to the new config if needed. - Security (
xpack.security.enabled) defaults tofalseto preserve the previous plain-HTTP behavior. Override by addingES_SETTING_XPACK_SECURITY_ENABLED(or anyES_SETTING_XPACK_SECURITY_*variable) in the add-on'senv_varsoption. - Fixed the
env_varsadd-on option, which previously had no effect: variables are now exported before Elasticsearch starts. - Removed the
ingest-attachmentplugin install: it is a bundled module since Elasticsearch 8.0. - Startup persistence logic rewritten as a proper init script (
/usr/local/bin/addon-init.sh) instead of line-number-based entrypoint patching. - Added
updater.jsonso upstream 8.19.x releases are tracked automatically (pinned to the 8.19 line: 9.x cannot read indices created in 7.x). - The upstream 8.x image ends the build as a non-root user with a read-only entrypoint; the Dockerfile now switches to root for the build steps that patch/install into it. The image stays root at runtime too (unchanged from 7.17.9): the upstream entrypoint no longer drops privileges itself, and
addon-init.shneeds to chown/move pre-existing/datacontent that may be owned by root from earlier installs. env_varsnames starting with a digit are now rejected before export instead of crashing the entrypoint.- Fixed a startup failure (
mv: cannot move '/data/config' ... Permission denied) on upgrade from an existing 7.17.9 install, caused by an earlier fix in this same release that switched the runtime user to non-root before this fix was in place.
8.14.3-3 (2026-06-19)
- Fix startup failing with
chroot: cannot change root directoryby allowingcapability sys_chrootin the AppArmor profile (#2709) - Fix AppArmor profile name (was
inadyn_addon, colliding with several other add-ons); renamed toelasticsearch_addon
8.14.3-2 (2025-11-18)
-
8.14.3-1 (2025-11-18)
- Added
env_varsoption to support custom environment variables from the add-on configuration.
- Added
-
BREAKING CHANGE : upgrade to v8.14.3. You'll need to rebuild your indexes
v7
- Implemented healthcheck
- WARNING : update to supervisor 2022.11 before installing
- Add codenotary sign
- New standardized logic for Dockerfile build and packages installation
- Initial build