John Paul Soliva 29c71e972a fix(docker): propagate container env through s6 to cont-init and main CMD ... s6-overlay's /init scrubs the environment before invoking both /etc/cont-init.d/* scripts and the container's CMD wrapper. As a result, ENV directives from the Dockerfile (HERMES_HOME=/opt/data, HERMES_WEB_DIST, …) and compose-time `environment:` entries (HERMES_UID, HERMES_GID) never reached the scripts that actually use them. Three concrete failures observed on macOS Docker Desktop with `~/.hermes:/opt/data`: * stage2-hook.sh ran with HERMES_UID unset → no UID remap, hermes user stayed at UID 10000 instead of the host user's UID. * skills_sync.py (invoked from stage2-hook) ran with HERMES_HOME unset → get_hermes_home() fell back to Path.home()/.hermes, populating a shadow $HERMES_HOME/.hermes/skills tree on the mounted volume (visible on the host as ~/.hermes/.hermes/skills). * The main `hermes gateway run` process inherited HOME=/root from the /init context (s6-setuidgid doesn't update HOME), so libraries resolving XDG_STATE_HOME via $HOME tried to write to /root/.local/state/hermes/gateway-locks/ and failed with EACCES, preventing the Discord adapter from acquiring its bot-token lock. Three surgical changes restore correct env flow: 1. The auto-generated /etc/cont-init.d/01-hermes-setup wrapper now uses `#!/command/with-contenv sh`, matching the pattern already used by docker/cont-init.d/02-reconcile-profiles. The container env (Dockerfile ENV + compose `environment:`) now reaches stage2-hook.sh and the skills_sync.py subprocess it spawns. 2. docker/main-wrapper.sh also switches to `#!/command/with-contenv sh`. The container CMD (`gateway run`, `chat`, `setup`, …) now sees HERMES_HOME and the other container-level env vars. 3. docker/main-wrapper.sh exports HOME=/opt/data before `s6-setuidgid hermes`. with-contenv populates HOME from the /init context (/root); s6-setuidgid drops privileges but does not update HOME. The hermes user's home per /etc/passwd is /opt/data, so the explicit override matches passwd. No behavior change for the non-buggy paths: the s6-supervised services already used with-contenv, and HOME=/opt/data only affects processes that resolved $HOME-based paths to /root (silently broken).		2026-05-26 13:41:21 +09:00
..
cont-init.d	fix(docker): make s6 lifecycle work for the unprivileged hermes user	2026-05-25 12:23:23 +10:00
s6-rc.d	fix(docker): make s6 lifecycle work for the unprivileged hermes user	2026-05-25 12:23:23 +10:00
entrypoint.sh	docs(docker): deprecation warning in entrypoint.sh shim	2026-05-24 18:05:33 -07:00
main-wrapper.sh	fix(docker): propagate container env through s6 to cont-init and main CMD	2026-05-26 13:41:21 +09:00
SOUL.md	feat(docker): add Docker container for the agent (salvage #1841) (#3668)	2026-03-28 22:21:48 -07:00
stage2-hook.sh	fix(security): tighten .env file permissions to 0600 at all creation sites	2026-05-25 03:40:47 -07:00