Files
archie/docker-compose.yml
T
sam fd1abdd6c8 fix(deploy): stop the agent stanza starting, and pull agent images
The agent service created a container that exited 0 immediately while
compose reported it as "Started", which reads like a crash loop. A build
profile keeps it out of `up -d`; naming it still works for build and pull.

containers.pull_policy was "if-not-present", which is not a recognised
value -- the pool pulls only when it is "always" or "missing", so the
typo disabled pulling outright and the deployed agent image drifted a day
behind the daemon. Watchtower cannot cover for it: agent containers are
spawned per task, and it only restarts long-running ones.
2026-07-31 01:51:19 +10:00

92 lines
3.6 KiB
YAML

# archie-core stack: daemon, NATS, and agent containers.
#
# Start: docker compose up -d
# Stop: docker compose down
# Logs: docker compose logs -f archied
services:
# ── NATS JetStream ────────────────────────────────────────────────
nats:
image: nats:2.14-alpine3.22
command: -js -m 8222
ports:
- "4222:4222" # client
- "8222:8222" # monitoring (http://localhost:8222)
volumes:
- nats_data:/data
restart: unless-stopped
healthcheck:
test: ["CMD", "wget", "-q", "-O", "-", "http://localhost:8222/healthz"]
interval: 10s
timeout: 5s
retries: 5
# ── archie daemon ──────────────────────────────────────────────────
archied:
image: git.catlow.cloud/sam/archied:latest
# Single config, mounted from outside the repo. Nothing in the working
# tree is required at runtime: a bind mount whose source is missing is
# created as a directory, and the loader rejects a directory, so a
# repo-root config file would take the daemon down on a fresh clone.
# See deployments/docker-nats-stack.toml for the template.
command: -config /etc/archie/config.toml
extra_hosts:
- "host.docker.internal:host-gateway"
ports:
- "8484:8484" # web dashboard
environment:
- ARCHIE_GITEA_TOKEN
- ARCHIE_GITEA_TOKEN_ARCHIE
- HEYARCHIE_TELEGRAM_BOT_TOKEN
- DEEPSEEK_API_KEY
volumes:
- ${HOME}/.config/archie/config.toml:/etc/archie/config.toml:ro
- /var/lib/archie/work:/var/lib/archie/work
- /var/lib/archie/db:/var/lib/archie
- /var/run/docker.sock:/var/run/docker.sock
depends_on:
nats:
condition: service_healthy
restart: unless-stopped
# ── agent image (built once, spawned per task by the daemon) ───────
# Not a long-running service: the daemon starts agent containers itself
# via the Docker socket. This stanza exists only so the image can be
# built locally.
#
# The build profile keeps `up -d` from starting it. Without it compose
# creates a container that exits 0 immediately and still reports
# "Started", which reads like a crash loop. Naming the service explicitly
# still works without activating the profile:
#
# docker compose build agent (also: task docker-build)
# docker compose pull agent -- plain `pull` skips profiled services
#
# Routine freshness is handled by the daemon, which pulls this image per
# task: see containers.pull_policy in the config. Watchtower cannot do it
# -- it only restarts long-running containers, and this is not one.
agent:
profiles: ["build"]
build:
context: .
dockerfile: Dockerfile
image: git.catlow.cloud/sam/archie-agent:latest
# ── deploy watcher ──────────────────────────────────────────────────
# Polls the registry for new archied/archie-agent images (pushed by
# .gitea/workflows/deploy.yml on merge to main) and restarts the
# containers that changed. Registry auth comes from the host's
# existing `docker login` config, mounted read-only.
watchtower:
image: nickfedor/watchtower
environment:
- DOCKER_CONFIG=/
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ${HOME}/.docker/config.json:/config.json:ro
command: --interval 60 --cleanup archie-core-archied-1
restart: unless-stopped
volumes:
nats_data: