Developer Tools
Docker Compose Generator
Generate a docker-compose.yml file with services, ports, volumes, environment, depends_on, and healthchecks. Live validation, ready-made templates.
Quick start
Load a sample or add a service template
Every choice updates the compose file on the right as you edit. Samples are realistic and ready to docker compose up.
Sample stacks
Add a service from a template
Compose specification version
Docker Compose v2 ignores the version field. Use Latest unless a downstream tool requires the legacy field.
Service 1
web
Source
Port mappings
Volumes
Environment variables
No environment variables yet. Reference an outside .env file value with ${VAR} to keep secrets out of the file.
Top-level named volumes
Add a named volume here when you want Docker (not the host) to manage persistent data, like postgres_data.
Top-level networks
Compose creates a default bridge network automatically. Add a named network here only if you need a non-default driver, like overlay, or a network that already exists outside of Compose.
docker-compose.yml
services:
web:
image: "nginx:1.27-alpine"
restart: unless-stopped
ports:
- "80:80"
volumes:
- "./nginx.conf:/etc/nginx/nginx.conf:ro"
- "./public:/usr/share/nginx/html:ro"
Save as docker-compose.yml in your project root and run docker compose up to start every service.
Review
No issues found. The compose file looks good.
How to use
- Click a sample stack at the top to seed the file with a working multi-service composition, or click a service template (nginx, postgres, mysql, redis, mongodb, node app, python app, adminer, mailhog, traefik) to add one service at a time.
- Edit each service: rename it, switch between an image tag and a local Dockerfile build, set the restart policy, add port mappings, add bind mounts or named volumes, add environment variables, and pick which other services it depends_on.
- Optional: enable a healthcheck and tune test, interval, timeout, retries, and start_period. The default test uses curl against localhost.
- Add top-level named volumes for any persistent data (postgres_data, mongo_data). Add networks only if you need a non-default driver like overlay.
- Read the Review panel as you edit, errors block a working compose file, warnings flag practices you usually want to fix, and notes explain context.
- Click Copy YAML, paste into a file named docker-compose.yml in your project root, then run docker compose up to start every service.
About this tool
Docker Compose Generator builds a complete docker-compose.yml file from a list of services, top-level named volumes, and named networks, with the YAML produced by a deterministic in-browser writer (no library, no upload). Each service supports the fields most stacks actually use: image or local build context, container_name, restart policy (unless-stopped, always, on-failure, no), command, working_dir, port mappings (host:container with TCP or UDP), bind mounts and named volumes (with optional read-only flag), environment variables, depends_on, networks, and an opt-in healthcheck block with test, interval, timeout, retries, and start_period. One-click templates seed common services with sensible defaults: nginx with a config bind mount, postgres with a persistent volume and a working pg_isready healthcheck, mysql and mariadb with credentials, redis with appendonly persistence, mongodb with root credentials, a Node.js or Python app that builds from a local Dockerfile, adminer and mailhog for local development, and traefik with the Docker provider. Sample stacks load multi-service compositions you can docker compose up right away: web + Postgres, PHP + MySQL + nginx, WordPress + MySQL, and Node + MongoDB + Redis. The YAML writer quotes only the strings that actually need quoting (leading dash, leading at, colons, hashes, YAML keywords like yes / no / on / off, strings that look like numbers, empty strings, dollar-prefixed env references) so the output matches the style of compose files Docker itself ships. A review panel surfaces real issues live: duplicate service names, host port collisions across services, depends_on pointing at a service that does not exist, named volumes referenced but not declared at the top level, latest or untagged images, environment variables that look like secrets, privileged host ports, and the legacy version field that Compose v2 ignores. The compose specification version selector defaults to Latest (omits the version line, which Compose v2 prefers) but lets you target version 3.9 or 3.8 if a downstream tool still requires it. Adding a templated service that uses a named volume (for example postgres_data) automatically declares that volume at the top level so the file is immediately valid. Everything runs in your browser. Service names, environment values, ports, and configuration never leave your device.
Free to use. Works in your browser. No signup, no login.
Related tools
You may also like
Dockerfile Generator
Build a production Dockerfile with multi-stage build, non-root user, BuildKit cache, and healthcheck.
Open tool
DeveloperGitignore Generator
Build a .gitignore from curated language, framework, editor, and OS templates.
Open tool
DeveloperNginx Config Generator
Build a production nginx server block with modern TLS, HTTP/2, HSTS, gzip, and proxy headers.
Open tool
DeveloperSSH Config Generator
Build a clean OpenSSH ~/.ssh/config from a form with validation and copy-paste output.
Open tool
DeveloperDatabase Connection String Builder
Generate connection URIs with per-driver defaults, TLS toggles, masking, and ready-to-paste env lines.
Open tool
DeveloperYAML Formatter
Pretty print and validate YAML with consistent indent, sorted keys, and clear errors.
Open tool