From 2d59bb44c37dcb37d6dd8de42f5cee6837660df3 Mon Sep 17 00:00:00 2001 From: Hermes Date: Fri, 22 May 2026 13:03:51 -0400 Subject: [PATCH] fix: remove venv volume mount conflicting with upstream entrypoint.sh MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- ai/compose.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/ai/compose.yml b/ai/compose.yml index ca5f181..3126c2b 100755 --- a/ai/compose.yml +++ b/ai/compose.yml @@ -61,8 +61,6 @@ services: - /mnt/HoardingCow_docker_data/Syncthing/telos-ro:/opt/data/telos-ro:ro # Syncthing-shared inbox — write tasks here, they sync to user's laptop - /mnt/HoardingCow_docker_data/Syncthing/telos-rw:/opt/data/telos-rw:rw - # Persist Python venv across container recreation (Matrix bridge deps, etc.) - - /mnt/HoardingCow_docker_data/Hermes/venv:/opt/hermes/.venv devices: - /dev/kfd:/dev/kfd - /dev/dri:/dev/dri