hermes - 💡(How to fix) Fix [Bug] v0.14.0 Docker image: Telegram bot fails on launch with --user flag

Bug Description

After updating from v0.13.0 to v0.14.0 Docker image (nousresearch/hermes-agent:latest), the Hermes gateway starts but never connects to Telegram. The container logs show repeated SIGTERM signals and the Telegram adapter never initializes.

Environment

• Host: Ubuntu VPS
• Docker run flags include: --user $(id -u):$(id -g) (UID 1000, GID 1000)
• Mount: /home/eralus/hermes:/opt/data
• Image: nousresearch/hermes-agent:latest (v0.14.0, released 2026-05-16)

Symptoms

• Container starts, gateway runs
• Telegram never connects — no messages sent or received
• Container logs show WARNING at startup and periodic SIGTERM

Workaround Found

bash docker exec -u root hermes chown -R 1000:1000 /opt/hermes/.venv docker exec hermes uv pip install python-telegram-bot --python /opt/hermes/.venv/bin/python3 docker restart hermes

After applying the workaround and restarting, Telegram connectivity is restored.

Hypothesis

Either:

1. v0.14.0's .venv directory was built/shipped with root-only permissions, breaking Python module imports when --user forces UID 1000.
2. python-telegram-bot was omitted from the core venv due to the new lazy-deps feature and is not automatically installed for the Telegram adapter.

Reproduction

1. Run v0.13.0 with --user 1000:1000 and Telegram configured → works
2. Pull latest (v0.14.0) and restart → Telegram dead
3. Apply workaround above → works again

Suggested Fix

Either ship .venv with world-readable permissions, or ensure python-telegram-bot is eagerly installed in the Docker image's venv for all messaging adapters.