power-compare/docker-compose.yml
dlawler489 ba070e0ad5
All checks were successful
Build and Push Docker Image / build-and-push (push) Successful in 8s
Fix env_file path for Docker-outside-of-Docker deploy
The stack manager runs docker compose inside its own container (talking
to the host daemon over the mounted socket), so env_file paths resolve
against its filesystem, not the host's -- unlike volume bind-mount
sources, which the daemon resolves against the real host. Point env_file
at the stack manager's own data mount instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-09 11:25:42 +10:00

23 lines
1.1 KiB
YAML

services:
power-compare:
image: git.plexultra.com/dlawler489/power-compare:main
ports:
- "8000:8000"
env_file:
# `docker compose` here runs *inside* the stack manager's own
# container (Docker-outside-of-Docker via the mounted host socket),
# so this path is resolved against ITS filesystem, not the host's --
# it must live under the stack manager's own data mount, in a
# directory outside the git checkout that gets wiped/re-cloned each
# deploy. On this host that's /Users/davidlawler/docker/dockhand,
# bind-mounted into the stack manager container as /app/data.
- /app/data/power-compare-persistent/.env
environment:
- DB_PATH=/data/power_compare.db
volumes:
# Bind-mount SOURCE paths, by contrast, are resolved by the real
# Docker daemon against the actual host filesystem (the daemon isn't
# inside the stack manager's container) -- so this one stays a real
# host path, not an /app/data/... one.
- /Users/davidlawler/docker/power-compare-data/data:/data
restart: unless-stopped