docker-compose
Installation
SKILL.md
🧩 Docker Compose
Where this fits
The container skills:
- dockerfile — one image per service, plus the
.dockerignorethat defines its build context - docker-compose (this skill) — wires those images to datastores, networks, volumes and health gates
- container-hardening — reviews how containers run in production. When a compose file is the production deploy (a VM running
docker compose up -d), it gets that full review; a dev stack built here is only checked for what hurts the laptop - container-debug — when a container won't start, stay up or connect: reads the runtime's own record, matches the symptom, proves the cause, and routes the fix back to the skill that owns it
- docker-swarm — reviews or designs a Swarm cluster and the stack files
docker stack deployruns
Run dockerfile first. Compose orchestrates images; it cannot repair one. Most "compose is broken" reports are an image that doesn't start, doesn't answer its healthcheck, or dies on SIGTERM — and no amount of compose configuration fixes any of those.
It leans on two reference docs:
- service-catalog.md — per-service definitions: image, healthcheck, volume path, env vars, connection string
- environments.md —
.envvs.env.example, override files, secret handling, dev/prod divergence