9.1 Compose Purpose

Compose's purpose is to replace the manual, error-prone process of issuing many individual docker commands to set up a multi-container application with a single, declarative file that fully describes the application's services, networking, and storage, then drives the entire setup with one straightforward command.

The Problem Compose Solves

Setting up a multi-container application manually requires remembering and correctly sequencing many individual commands — creating networks, starting containers in the right order with the right flags — a process that's tedious, error-prone, and difficult for someone else to reliably reproduce.

docker network create app-net
docker run -d --name db --network app-net -v pgdata:/var/lib/postgresql/data postgres:16
docker run -d --name api --network app-net -p 8080:8080 -e DATABASE_URL=postgres://db:5432/app myapi:1.0

How Compose Addresses This

A single Compose file captures this entire setup declaratively, removing the need to remember or correctly sequence individual commands.

services:
  db:
    image: postgres:16
    volumes:
      - pgdata:/var/lib/postgresql/data
  api:
    build: .
    ports:
      - "8080:8080"
    environment:
      - DATABASE_URL=postgres://db:5432/app
    depends_on:
      - db

volumes:
  pgdata:

docker compose up -d

Why This Declarative Approach Is Valuable

Anyone with access to the Compose file can reproduce the exact same multi-container setup reliably, without needing to understand or correctly replicate a specific sequence of manual commands.

git clone https://github.com/example/myapp.git
cd myapp
docker compose up -d

Why Understanding Compose's Purpose Matters

Recognizing Compose's core purpose — replacing manual, sequential command execution with a single, reliable, declarative definition — clarifies why it has become the standard tool for defining and sharing multi-container application setups, particularly for local development and smaller-scale deployments.