Docker Compose: Multi-Container Apps Made Simple

Running docker run is fine for one container. But what if your app needs a database? And a cache? And a frontend? Do you really want to run 4 commands in a specific order every time you restart your laptop?

Enter Docker Compose.

Introduction

Docker Compose is a tool that lets you define and run multi-container Docker applications. You create a single file called docker-compose.yml, define everything your app needs (containers, networks, volumes), and start it all with one command.

The docker-compose.yml File

This is where the magic happens. It uses YAML (Yet Another Markup Language), which relies on indentation.

A Real Example: Ghost Blog + MySQL

Here is a full stack for a Ghost blog. It needs the Ghost app AND a MySQL database.

version: '3.8'

services:
  ghost-app:
    image: ghost:latest
    ports:
      - "8080:2368"
    environment:
      - database__client=mysql
      - database__connection__host=db
      - database__connection__user=root
      - database__connection__password=secret
      - database__connection__database=ghost
    depends_on:
      - db

  db:
    image: mysql:8.0
    environment:
      - MYSQL_ROOT_PASSWORD=secret
      - MYSQL_DATABASE=ghost
    volumes:
      - db-data:/var/lib/mysql

volumes:
  db-data:

---

Essential Commands

Once you have your docker-compose.yml file, you only need these commands:

Start Everything

Check Status

Stop and Clean Up

---

Key Concepts Explained

1. Services

A “service” is just a fancy name for a container in the context of your app. In the example above, ghost-app and db are services.

2. Ports ("Host:Container")

"8080:2368" means “Forward port 8080 on my laptop to port 2368 inside the container.” You open localhost:8080 in your browser.

3. Environment Variables

Inject configuration like passwords, API keys, or debug flags without changing the image code.

4. Volumes

volumes: - db-data:/var/lib/mysql This maps a persistent storage area to the database folder. Even if you destroy the db container, the data in db-data survives. When you restart, your blog posts are still there.

5. depends_on

Tells Docker to start the db before the ghost-app.

---

Hands-On Challenge

1. Create a folder my-blog and enter it.
2. Create a file named docker-compose.yml and paste the Ghost example code above.
3. Run docker compose up -d.
4. Open http://localhost:8080 in your browser. You should see the Ghost blog!
5. Run docker compose down to clean up.

---

Key Takeaways

• One File: Define your whole stack (app, db, cache) in docker-compose.yml.
• One Command: docker compose up -d launches everything.
• Networking: Containers talk to each other by service name (e.g., db), not IP.
• Persistence: Use Volumes to keep database data safe even if containers crash.
• Production: Docker Compose is great for dev and small servers. For massive scale, you’d upgrade to Kubernetes (which uses similar YAML concepts).

🧠

Test Your Knowledge

Score: 0/5

Take a quick 5-question quiz to check your understanding.

Start Quiz

Next

0 /5

Retake Quiz