Docker Compose Generator — Free Online Tool

Select your services and get a production-ready docker-compose.yml with volumes, networks, and environment variables.

What is Docker Compose?

Docker Compose is a tool for defining and running multi-container applications. With a single docker-compose.yml file, you define your entire application stack — web servers, databases, caches, and other services — along with how they connect and communicate. A single docker-compose up command starts everything.

Docker Compose is ideal for local development environments, CI/CD pipelines, and even small production deployments. It eliminates the "it works on my machine" problem by ensuring every developer uses the same environment configuration.

Common Docker Compose Stacks

  • Node.js + PostgreSQL + Redis: A typical REST API backend with relational storage and caching
  • Python + MySQL: Common for Django or Flask web applications
  • Nginx + Node.js: Nginx as a reverse proxy in front of your Node.js application
  • Full-stack: Nginx + Node.js + PostgreSQL + Redis: Production-like setup with reverse proxy, API, database, and cache

Docker Compose Volumes & Networks Tips

  • Always use named volumes for database data to persist between container restarts
  • Use custom bridge networks for service-to-service communication — services can reach each other by service name
  • Use .env files for sensitive values (passwords, API keys) instead of hardcoding in compose files
  • Set restart: unless-stopped for production services to auto-restart on failure
  • Use healthcheck to delay dependent services until your database is ready

Docker Compose Best Practices for Production

Docker Compose is excellent for local development and simple deployments, but moving from development to production requires careful consideration of security, performance, and reliability. Here are the practices that separate development-grade from production-grade Compose configurations.

Security Hardening

  • Never hardcode secrets: Use env_file or Docker secrets instead of putting passwords directly in docker-compose.yml. The compose file is typically committed to Git, exposing all hardcoded credentials.
  • Pin image versions: Use node:20.11-alpine instead of node:latest. The latest tag can change unexpectedly, breaking your build or introducing vulnerabilities.
  • Use read-only filesystems: Add read_only: true to containers that don't need to write to disk. This limits the blast radius of container compromises.
  • Drop capabilities: Use cap_drop: [ALL] and selectively add back only needed capabilities with cap_add. Most containers don't need the default Linux capabilities.

Performance and Reliability

  • Resource limits: Always set mem_limit and cpus to prevent a single container from consuming all host resources. A memory-leaking container without limits can crash the entire server.
  • Health checks: Define healthcheck for each service so Docker can detect and restart unhealthy containers automatically. Use actual endpoint checks, not just process existence.
  • Restart policies: Use restart: unless-stopped for production services. This survives server reboots while still allowing manual stops for maintenance.
  • Logging configuration: Set logging.options.max-size and max-file to prevent container logs from filling up disk space. Default Docker logging has no size limit.

Frequently Asked Questions about Docker Compose

What is the difference between docker compose up and docker compose start?

docker compose up creates and starts containers from scratch, pulling or building images as needed. docker compose start only restarts containers that were previously created and stopped — it cannot create new ones. Use docker compose up -d for detached (background) mode. Add --build to force image rebuilds when your Dockerfile changes.

How do services communicate with each other in Docker Compose?

Services on the same Docker Compose network reach each other using the service name as the hostname. If your database service is named db, your application connects to db:5432 instead of localhost:5432. Docker Compose automatically creates a default bridge network for all services defined in the same compose file. You can create custom named networks for more control.

How do I persist database data between container restarts?

Use named volumes in your compose file. Without a volume, all data inside a container is lost when it stops. Define a volume under the service: volumes: - postgres_data:/var/lib/postgresql/data, then declare it at the top level: volumes: postgres_data:. Named volumes are managed by Docker and persist across docker compose down — only docker compose down -v removes them.

What does restart: unless-stopped mean in Docker Compose?

restart: unless-stopped means Docker will automatically restart the container if it crashes or if the Docker daemon restarts (e.g., after a server reboot), but it will not restart a container that you explicitly stopped with docker compose stop. This is the recommended setting for production services. Other options: no (never restart), always (always restart, even after explicit stop), on-failure (restart only on non-zero exit code).

Related Developer Tools