fix: move run-multi-gateways.sh into build context, bake into image #50

Hermes · 2026-05-23T01:37:15Z

Hermes commented

2026-05-23 01:37:15 +00:00

What

Move run-multi-gateways.sh from repo root to ai/hermes/ (inside the Docker build context)
COPY the script into the image at /usr/local/bin/run-multi-gateways.sh so it's available at container startup without relying on a manually-placed root-owned copy on the persistent volume
Fix compose.yml entrypoint to reference /usr/local/bin/run-multi-gateways.sh instead of the old /opt/data/hermes-tools/ path

Why

The previous setup placed run-multi-gateways.sh at the repo root and referenced it from /opt/data/hermes-tools/ (a persistent volume path). This caused:

File not in build context — the Dockerfile build context is ./hermes, so COPY run-multi-gateways.sh couldn't reach it from the repo root
Root-owned copy on volume — a separate copy had to be manually placed in /opt/data/hermes-tools/ owned by root, with trailing spaces before backslash continuations that broke bash parsing (\ vs \$), causing env: ' ': No such file or directory
Messy repo root — the file doesn't belong at the top level of the compose repo

Changes

File	Change
`ai/hermes/run-multi-gateways.sh`	Moved from repo root
`ai/hermes/Dockerfile`	Added `COPY --chmod=0755 run-multi-gateways.sh /usr/local/bin/run-multi-gateways.sh`
`ai/compose.yml`	Entrypoint now calls `bash /usr/local/bin/run-multi-gateways.sh`

## What - **Move** `run-multi-gateways.sh` from repo root to `ai/hermes/` (inside the Docker build context) - **COPY** the script into the image at `/usr/local/bin/run-multi-gateways.sh` so it's available at container startup without relying on a manually-placed root-owned copy on the persistent volume - **Fix** compose.yml entrypoint to reference `/usr/local/bin/run-multi-gateways.sh` instead of the old `/opt/data/hermes-tools/` path ## Why The previous setup placed `run-multi-gateways.sh` at the repo root and referenced it from `/opt/data/hermes-tools/` (a persistent volume path). This caused: 1. **File not in build context** — the Dockerfile build context is `./hermes`, so `COPY run-multi-gateways.sh` couldn't reach it from the repo root 2. **Root-owned copy on volume** — a separate copy had to be manually placed in `/opt/data/hermes-tools/` owned by root, with **trailing spaces before backslash continuations** that broke bash parsing (`\ ` vs `\$`), causing `env: ' ': No such file or directory` 3. **Messy repo root** — the file doesn't belong at the top level of the compose repo ## Changes | File | Change | |------|--------| | `ai/hermes/run-multi-gateways.sh` | Moved from repo root | | `ai/hermes/Dockerfile` | Added `COPY --chmod=0755 run-multi-gateways.sh /usr/local/bin/run-multi-gateways.sh` | | `ai/compose.yml` | Entrypoint now calls `bash /usr/local/bin/run-multi-gateways.sh` |

Hermes added 11 commits 2026-05-23 01:37:16 +00:00

fix: remove venv volume mount conflicting with entrypoint.sh e4117cd3d5

The volume mount at /mnt/HoardingCow_docker_data/Hermes/venv overrides the
container's built .venv with an empty or stale host directory, causing
entrypoint.sh line 62 to fail on 'source .venv/bin/activate' (set -e).

The Docker image already builds a complete venv — no need to persist it.

feat: bake Matrix bridge deps into Docker image instead of volume mount bce336c4fd

- Add libolm-dev system dep (required by mautrix[encryption])
- Add mautrix[encryption] + openai pip packages to build
- These were previously installed inline at container startup and
  persisted via the fragile venv volume mount (now removed)

fix: add missing command: gateway run to hermes service 45a224eb7f

Without this,  is empty and entrypoint.sh runs bare 'hermes'
which defaults to interactive chat mode. With a non-TTY stdin
this exits immediately with prompt_toolkit's 'Input is not a
terminal' warning, causing a container restart loop.

The profile gateways (run-multi-gateways.sh) were unaffected
because the script passes 'gateway run' explicitly.

fix: add missing command: gateway run to hermes service d8a1ebcd96

Without this,  is empty and entrypoint.sh runs bare 'hermes'
which defaults to interactive chat mode. With a non-TTY stdin
this exits immediately with prompt_toolkit's 'Input is not a
terminal' warning, causing a container restart loop.

The profile gateways (run-multi-gateways.sh) were unaffected
because the script passes 'gateway run' explicitly.

Merge remote-tracking branch 'origin/fix/remove-venv-mount' ef6e0e57b6

Merge remote-tracking branch 'origin/fix/hermes-build' eb3795d9e3

fix: use full hermes path and gosu in multi-gateway launcher 146add2a64

- Use /opt/hermes/.venv/bin/hermes (full path) — not on PATH
  before entrypoint.sh sources the venv
- Wrap with gosu hermes to avoid root guard in gateway run
- Add error check if hermes binary doesn't exist

fix: use env to force API_SERVER_ENABLED=false in multi-gateway launcher 645d519030

Shell prefix didn't work with nohup+gosu chain - Docker compose
env var API_SERVER_ENABLED=true leaked through. Using 'env'
command guarantees the override is in the child process env.

fix: also clear API_SERVER_KEY for profile gateways e8075fb71b

Line 1521 in gateway/config.py: if api_server_enabled or api_server_key:
The compose.yml sets API_SERVER_KEY=hermes_local_key, which was enough
to enable the API server even with API_SERVER_ENABLED=false.

Merge remote-tracking branch 'origin/fix/hermes-build' 5765dc6004

fix: move run-multi-gateways.sh into ai/hermes/ and bake into image

Build Hermes agent / build (pull_request) Has been cancelled

Details

Build ollama (gfx906) / build (pull_request) Has been cancelled

Details

c1cd9d31e9

gortium merged commit 3d90f57e7f into master

2026-05-23 02:12:52 +00:00

gortium referenced this issue from a commit

2026-05-23 02:12:54 +00:00

Merge pull request 'fix: move run-multi-gateways.sh into build context, bake into image' (#50) from fix/multi-gateway-path into master