# Docker Compose

> Docker Compose V2 and Compose Specification expertise for writing correct compose.yaml and docker-compose.yml files. Use when the user mentions Docker Compose, compose.yaml, docker-compose.yml, docker compose CLI, multi-container apps, profiles, healthchecks, depends_on, networks, volumes, secrets, build contexts, or avoiding deprecated V1 patterns.

- **Type:** Skill
- **Install:** `agentstack add skill-gordonmurray-data-engineering-skills-docker-compose`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [gordonmurray](https://agentstack.voostack.com/s/gordonmurray)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [gordonmurray](https://github.com/gordonmurray)
- **Source:** https://github.com/gordonmurray/data-engineering-skills/tree/main/docker-compose

## Install

```sh
agentstack add skill-gordonmurray-data-engineering-skills-docker-compose
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Docker Compose V2 Expert

Use this skill to write, review, and modernize Docker Compose files using the current Compose Specification and `docker compose` V2 CLI.

## Current Facts

- The top-level `version` property is obsolete. Compose keeps it only for backward compatibility and warns when it is used.
- Compose validates against the most recent schema regardless of `version`.
- Use `docker compose`, not the old standalone `docker-compose` command, unless supporting a pinned legacy environment.
- Default file names are `compose.yaml` and `compose.yml`; `docker-compose.yml` remains widely supported.
- Root-level keys commonly include `services`, `networks`, `volumes`, `configs`, and `secrets`.
- Current example image majors as of June 2026: PostgreSQL 18 and Redis 8. Pin exact patch/minor versions for production.

## How To Use

1. Start with `services:` and no `version:` field.
2. Add only the networks, volumes, secrets, configs, profiles, and build settings required for the user’s workflow.
3. Use healthchecks plus long-form `depends_on` when startup readiness matters.
4. Bind sensitive ports to `127.0.0.1` unless external access is required.

## Review Checklist

- No top-level `version:`.
- `services:` is plural and at the root.
- Service names are stable and lowercase.
- Images are pinned for production; avoid `latest` except in disposable examples.
- Secrets are not embedded in YAML; use env vars, `.env`, secret files, or platform secrets.
- Persistent database state uses named volumes.
- Development bind mounts are explicit and use `:ro` when possible.
- Healthchecks use commands available inside the image.
- Resource limits are explicit where runaway memory/CPU use is risky.

## Common Patterns

- PostgreSQL: use `postgres:18-alpine` for current examples unless project requirements say otherwise.
- Redis: use `redis:8-alpine` for current examples unless project requirements say otherwise.
- Internal databases should usually live only on a backend network and avoid host port exposure.
- Use `profiles` for optional services such as observability, admin tools, or one-off jobs.
- Use `docker compose config` to validate rendered configuration.

## Update Checklist

- Recheck Docker Compose docs for newly added keys such as `develop`, `interface_name`, or pull policy support before recommending them.
- Recheck upstream image tags before refreshing examples.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [gordonmurray](https://github.com/gordonmurray)
- **Source:** [gordonmurray/data-engineering-skills](https://github.com/gordonmurray/data-engineering-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** yes
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-gordonmurray-data-engineering-skills-docker-compose
- Seller: https://agentstack.voostack.com/s/gordonmurray
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.