Skill-Datei

Docker Compose Patterns

Name: Docker Compose Patterns
Author: srijan-at-qwertystars

Generate and review Docker Compose configurations for multi-container applications. Covers Compose V2 spec (compose.yaml), services, networks, volumes, configs, secrets, build context, multi-stage builds, depends_on with healthchecks, environment variables (.env, interpolation), profiles, extends, YAML anchors, watch mode, GPU support, multiple Compose files (override pattern), restart policies, resource limits, logging drivers, init containers, CI/CD patterns, and debugging. Triggers: "Docker Compose", "compose.yaml", "compose.yml", "multi-container Docker", "docker compose up", "docker compose build", "docker compose watch", "compose profiles", "compose healthcheck", "compose override". NOT for Kubernetes manifests, NOT for single Dockerfile without orchestration, NOT for Docker Swarm clustering without Compose, NOT for Podman-specific features.

srijan-at-qwertystars0 Sterne24.03.2026

Beruf
Kategorien: Container

Skill-Inhalt

Core Rules

Always use Compose V2 CLI: docker compose (space-separated). Never docker-compose (hyphenated, V1 deprecated).
Omit the version: field — it is deprecated and triggers warnings.
Prefer compose.yaml as the filename. docker-compose.yml still works but is legacy.
Use named volumes for persistent data. Never rely on anonymous volumes in production.
Always define healthchecks for services that other services depend on.
Set restart policies and resource limits for every production service.
Never hardcode secrets in compose files. Use Docker secrets, env_file, or CI injection.

File Structure

# compose.yaml — top-level keys

Verwandte Skills

Docker Compose Patterns | Skills Pool

Docker Compose Patterns

Core Rules

File Structure

Docker Compose Patterns

Core Rules

File Structure

Helm Chart Scaffolding

Python Observability

K8s Manifest Generator

Istio Traffic Management

Secrets Management

Gitops Workflow