# devops / orchestration / compose

Run Multiple Containers Easily

Running one container is fine, but real apps usually need a web server, a database, a cache, and an API. Starting each one manually with long docker run commands is painful. Docker Compose solves this instantly.

See a Compose File →Jump to commands

$ docker compose up -d✓

Networkapp_default created

Containerdb-1 Started

Containerweb-1 Started

StatusApp is online

File

Command

# overview

The "Combo Order" Concept

Docker Compose lets you define and run multi-container Docker applications using a single YAML file. It is heavily used in local development, automated testing, and small-scale production setups.

fast food analogy

🍔 The Combo Meal

Imagine ordering food: Burger = Web app, Fries = Database, Drink = Cache. Instead of ordering each item one by one, you order a "Combo #1". Docker Compose is the combo order for your containers.

efficiency

One File to Rule Them All

You declare networks, volumes, environment variables, and startup sequences inside docker-compose.yml. Docker reads it and provisions the entire stack.

# syntax

The Heart of Compose: docker-compose.yml

docker-compose.ymlYAML

1 2 3 4 5 6 7 8 9 10 11 12 13

version: "3.9"

services:
  web:
    image: nginx
    ports:
      - "80:80"

  db:
    image: mysql:8
    environment:
      MYSQL_ROOT_PASSWORD: root

What happens here?

services
Each container is called a service (e.g., web and db).
image & ports
The web service pulls the Nginx image and maps host port 80 to container port 80.
environment
The DB service spins up MySQL and automatically passes in the required root password.
execution
Both containers start together and run as a single, cohesive application.

# concepts

Advanced Compose Features

🌐 Networking (Service Discovery)

By default, Compose creates a single bridge network for the app. Containers can talk to each other using their service names as hostnames. The backend can reach the database simply by pinging db. No IP addresses needed!

⏱️ Startup Order (depends_on)

You can use depends_on: - db under your web service. This ensures the database container starts first before the web container starts. Note: It only waits for the container to start, not for the DB software to be fully ready.

🧱 Build from Source

Instead of using prebuilt images from Docker Hub, you can tell Compose to build a local Dockerfile by using build: . instead of image:. Great for local development.

💾 Volumes (Persistence)

Define a named volume at the bottom of the file, then map it to a service:

volumes: - db_data:/var/lib/mysql

If you delete the container, your database data remains safe in the volume.

🔐 Environment Variables

You can define env vars directly in the file, or use an external .env file (the cleaner way). Compose automatically detects the .env file in the same directory and loads the values.

# commands

Compose CLI Cheat Sheet

One command replaces many complex docker run strings. Manage the entire lifecycle of your application stack from this single CLI tool.

terminal

# Start the Application

$ docker compose up → Start everything (attaches logs to terminal)

$ docker compose up -d → Start everything in the background (detached)

$ docker compose up --build → Force a rebuild of custom images before starting

# Stop and Clean Up

$ docker compose down → Stop and remove containers + networks

$ docker compose down -v → Stop, remove containers, AND wipe volumes

# comparison

Docker Compose vs Docker Swarm

Feature	Docker Compose 🧩	Docker Swarm 🐳
Purpose	Local / simple multi-container setups	Production-grade clustering
Scaling	Manual (via CLI flags)	Automatic & Dynamic
Nodes	Single host machine	Multiple distributed hosts
Complexity	Simple 😊	Medium ⚙️

WHEN TO USE COMPOSE?

Use Docker Compose when you are developing locally, testing microservices, running basic CI/CD pipelines, or just learning Docker concepts before moving to a cluster.