CONTAINERS / Docker
Docker Compose Patterns
Establishes production patterns for compose.yaml: strict healthcheck dependencies, curl sidecars for scratch images, and secret masking.
“Use this skill when creating, modifying, or debugging Docker Compose configurations, even if the user just says they need to wire services together, add a database to their stack, or set up a local development environment with multiple containers. Covers service definitions, health checks, dependency ordering, volumes, networks, environment variables, and development overrides.”
01 / THE REASONING
Why this made the selection.
- Enforces condition: service_healthy on depends_on stanzas to prevent premature service crashes on unready databases and backends.
- Recommends validating Compose setups via docker compose config --quiet to avoid printing interpolated secrets and environment variables to build logs.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- skills/docker-compose-patterns/SKILL.md
- LICENSE
- skills/docker-compose-patterns/scripts/verify-compose.sh
Our findings
- The Apache appendix specifies Copyright 2026 Docker, Inc.
- Scratch and distroless containers that lack curl are instructed to share network namespaces with dedicated curl sidecars rather than polluting production images with debug binaries.
- Inspected helper only validates config quietly and propagates the Compose exit status.
- Definition distinguishes external volumes from Compose-managed volumes and service start from service health.
- Development-only bind mounts and debug ports go in compose.override.yaml, which Compose loads automatically.
Not established by this review
- docker compose up, config, and down commands were not executed against the Docker daemon.
- The references/service-dependencies.md and references/volumes-and-networks.md files were not read line-by-line.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add docker/skills/skills/docker-compose-patterns Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/docker/skills/tree/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-compose-patterns - Install the single skill directory using the pinned npx skills add command.
- Ensure local environment variables referenced in compose.yaml exist in .env before running validation.
Before you start
- Node.js runtime
- Docker Compose v2
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-compose-patterns/SKILL.md
Supports: summary, whySelected, bestFor, limitations
- Docker skills license ↗Checked
https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/LICENSE
Supports: license
https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-compose-patterns/scripts/verify-compose.sh
Supports: review, limitations, access, install
https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-compose-patterns/SKILL.md
Supports: upstreamDescription, review.notTested, review.reviewedAt