agnes-the-ai-analyst/docker-compose.host-mount.yml
ZdenekSrotyr 1acc89c486 fix(ci): move bind-mount of /data to separate overlay, fix CI smoke test
The CI smoke test failed because docker-compose.prod.yml forced a bind mount
to /data on the host — which doesn't exist on GitHub runners.

Split the bind mount into docker-compose.host-mount.yml, which is only
composed by the VM startup script (/data exists there, mounted from the
persistent disk). CI continues to use the default named volume.

Module startup script + auto-upgrade cron now compose all three:
  -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.host-mount.yml
2026-04-21 16:54:18 +02:00

21 lines
622 B
YAML

# Bind-mount overlay — replaces the `data` named volume with a bind mount
# to /data on the host.
#
# Use this when /data is a persistent disk mounted by the VM startup script,
# so Agnes data lives on the PD (not on the boot disk's Docker volume).
#
# Usage (combined with docker-compose.prod.yml):
# docker compose \
# -f docker-compose.yml \
# -f docker-compose.prod.yml \
# -f docker-compose.host-mount.yml \
# up -d
#
# Do NOT use this overlay in CI — /data does not exist on GitHub runners.
volumes:
data:
driver: local
driver_opts:
type: none
o: bind
device: /data