fix: remove venv volume mount conflicting with entrypoint.sh #49

Hermes · 2026-05-22T17:03:58Z

Hermes commented

2026-05-22 17:03:58 +00:00

Removes the /mnt/HoardingCow_docker_data/Hermes/venv:/opt/hermes/.venv volume mount from the hermes service.

Problem: This volume mount overrides the container's built-in .venv with whatever is on the host. On a fresh container start or after a clean build, an empty/missing host directory causes /opt/hermes/docker/entrypoint.sh line 62 (source .venv/bin/activate with set -e) to fail with:

/opt/hermes/docker/entrypoint.sh: line 62: /opt/hermes/.venv/bin/activate: No such file or directory

The old inline entrypoint (bash /opt/data/hermes-tools/install.sh && . /opt/hermes/.venv/bin/activate && uv pip install ...) masked this because it sourced the venv before reaching entrypoint.sh. The cleaned-up entrypoint (from fix/hermes-build) removed that guard, exposing the latent issue.

Fix: The Docker image already builds a complete venv in /opt/hermes/.venv — persisting it on the host was unnecessary and fragile.

Removes the `/mnt/HoardingCow_docker_data/Hermes/venv:/opt/hermes/.venv` volume mount from the hermes service. **Problem:** This volume mount overrides the container's built-in `.venv` with whatever is on the host. On a fresh container start or after a clean build, an empty/missing host directory causes `/opt/hermes/docker/entrypoint.sh` line 62 (`source .venv/bin/activate` with `set -e`) to fail with: ``` /opt/hermes/docker/entrypoint.sh: line 62: /opt/hermes/.venv/bin/activate: No such file or directory ``` The old inline entrypoint (`bash /opt/data/hermes-tools/install.sh && . /opt/hermes/.venv/bin/activate && uv pip install ...`) masked this because it sourced the venv before reaching entrypoint.sh. The cleaned-up entrypoint (from `fix/hermes-build`) removed that guard, exposing the latent issue. **Fix:** The Docker image already builds a complete venv in `/opt/hermes/.venv` — persisting it on the host was unnecessary and fragile.

Hermes added 1 commit 2026-05-22 17:03:59 +00:00

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

Build Hermes agent / build (pull_request) Has been cancelled

Details

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

Details

2d59bb44c3

The volume mount /mnt/HoardingCow_docker_data/Hermes/venv overrides the
container's built-in .venv with whatever is on the host. On a fresh start
or after a clean build, an empty/missing venv directory causes entrypoint.sh
line 62 (source .venv/bin/activate) to fail with set -e.

The Docker image already builds a complete venv — persisting it on the host
is unnecessary and fragile.

Hermes added 1 commit 2026-05-22 17:04:52 +00:00

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

Build Hermes agent / build (pull_request) Has been cancelled

Details

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

Details

567850bd13

- 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)

gortium merged commit 46f3b23a3f into master

2026-05-22 17:05:53 +00:00

gortium referenced this issue from a commit

2026-05-22 17:05:54 +00:00

Merge pull request 'fix: remove venv volume mount conflicting with entrypoint.sh' (#49) from fix/remove-venv-mount into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: gortium/compose#49