Siddharth Balyan 942adf6179 fix(docker): chown .venv to hermes so lazy_deps can install platform packages (#24841) ...

The Dockerfile permissions section made /opt/hermes/.venv readable but not
writable by the hermes runtime user.  Since the 2026-05-12 policy change
moved messaging packages (discord.py, telegram, slack, etc.) out of [all]
and into lazy_deps.py, the Docker image no longer ships with them
pre-installed.  At first gateway boot, lazy_deps.ensure() tries to
`uv pip install` them into the venv but fails with EACCES because
site-packages is root-owned.

The result: every messaging platform adapter silently fails to load inside
Docker containers, producing only a cryptic "discord.py not installed"
warning despite the gateway being correctly configured.

Two-part fix:

1. Dockerfile: add /opt/hermes/.venv to the existing chown -R hermes:hermes
   line so the default (UID 10000) case works out of the box.

2. docker/entrypoint.sh: extend the needs_chown block to also re-chown the
   .venv when HERMES_UID is remapped. Without this, the build-time chown
   becomes stale when someone uses the documented HERMES_UID override in
   docker-compose.yml.

Fixes #21536
Related: #17674, #21543, #21755

2026-05-13 11:55:07 +05:30

..

entrypoint.sh

fix(docker): chown .venv to hermes so lazy_deps can install platform packages (#24841)

2026-05-13 11:55:07 +05:30

SOUL.md

feat(docker): add Docker container for the agent (salvage #1841) (#3668)

2026-03-28 22:21:48 -07:00