Why Docker Compose for dev environment? - Purpose & Use Cases

The Big Idea

What if you could start your whole app with one simple command instead of dozens?

The Scenario

Imagine you are building a web app that needs a database, a cache, and a backend server. You start each service by typing long commands in separate terminal windows, setting ports and environment variables manually every time.

The Problem

This manual way is slow and confusing. You might forget a port number or environment setting. Starting or stopping services one by one wastes time. If you want to share your setup with a teammate, you have to explain all the commands again.

The Solution

Docker Compose lets you write a simple file describing all your services and how they connect. With one command, you start everything together. It keeps your setup consistent and easy to share, so you can focus on coding instead of managing services.

Before vs After

✗ Before

docker run -d -p 5432:5432 --name db postgres

docker run -d -p 6379:6379 --name cache redis

docker run -d -p 8000:8000 --name backend myapp

✓ After

docker-compose up -d

What It Enables

You can launch your entire development environment with a single command, saving time and avoiding mistakes.

Real Life Example

A developer shares a docker-compose.yml file with the team. Everyone runs the same command to get the app and its database running locally, making collaboration smooth and fast.

Key Takeaways

Manual service management is slow and error-prone.

Docker Compose automates starting multiple services together.

It makes sharing and reproducing environments easy.

Practice

1. What is the main purpose of using docker-compose.yml in a development environment?

easy

A. To build Docker images only

B. To define and run multiple containers with one command

C. To replace Docker CLI commands completely

D. To monitor container resource usage

Solution

1. Step 1: Understand Docker Compose role

   Docker Compose uses a YAML file to define multiple containers and their settings.

2. Step 2: Identify main benefit in dev

   It allows running all containers together with a single command, simplifying setup.

3. Final Answer:

   To define and run multiple containers with one command -> Option B

4. Quick Check:

   Compose = multiple containers, one command [OK]

Hint: Compose runs many containers with one file and command [OK]

Common Mistakes:

• Thinking Compose only builds images
• Believing Compose replaces all Docker CLI commands
• Confusing Compose with monitoring tools

2. Which of the following is the correct syntax to expose port 8080 on the host mapped to port 80 in a docker-compose.yml service?

easy

A. ports:
- "80:8080"

B. expose:
- "80:8080"

C. expose:
- "8080:80"

D. ports:
- "8080:80"

Solution

1. Step 1: Understand ports syntax in Compose

   The format is "host_port:container_port" to map host port to container port.

2. Step 2: Match ports for host 8080 to container 80

   To expose container port 80 on host port 8080, use "8080:80" under ports.

3. Final Answer:

   ports: - "8080:80" -> Option D

4. Quick Check:

   HostPort:ContainerPort = 8080:80 [OK]

Hint: Ports use host:container format [OK]

Common Mistakes:

• Reversing host and container ports
• Using expose instead of ports for host mapping
• Incorrect YAML indentation

3. Given this docker-compose.yml snippet, what will be the effect of the volume configuration?

services:
  app:
    image: myapp
    volumes:
      - ./src:/app/src

medium

A. The host's ./src folder is shared with /app/src inside the container

B. The container's /app/src folder is copied to host's ./src folder once

C. The container will have an empty /app/src folder

D. The volume will cause a syntax error

Solution

1. Step 1: Understand volume syntax in Compose

   Format "host_path:container_path" mounts host folder inside container.

2. Step 2: Analyze given volume mapping

   Host folder ./src is mounted to container path /app/src, sharing files live.

3. Final Answer:

   The host's ./src folder is shared with /app/src inside the container -> Option A

4. Quick Check:

   Volume mount = host folder shared inside container [OK]

Hint: Volumes share host folder inside container path [OK]

Common Mistakes:

• Thinking volume copies files only once
• Confusing source and target paths
• Assuming volume creates empty folder

4. You wrote this docker-compose.yml but get an error when running docker-compose up. What is wrong?

services:
  web:
    image: nginx
    ports:
      - "80:80"
    volumes:
      - ./html:/usr/share/nginx/html
    environment:
      - DEBUG=true
    command: nginx -g 'daemon off;'
    restart: always
  db:
    image: postgres
    environment:
      POSTGRES_PASSWORD: example
    volumes:
      - pgdata:/var/lib/postgresql/data
volumes:
  pgdata:

medium

A. The environment variable for db should use list syntax or key-value mapping consistently

B. The volume pgdata is not defined properly under volumes

C. The command for web service is invalid

D. The environment variable for db uses wrong syntax, should be a list

Solution

1. Step 1: Inspect YAML syntax in command field

   The command: nginx -g 'daemon off;' lacks quotes around the full string, causing YAML to parse it as separate unquoted scalars, leading to a syntax error.

2. Step 2: Confirm other sections are valid

   Environment uses valid list/map styles (mixed OK), volumes properly defined.

3. Final Answer:

   The command for web service is invalid -> Option C

4. Quick Check:

   Multi-word command needs full quotes or YAML list [OK]

Hint: YAML command with spaces: quote whole or use list [OK]

Common Mistakes:

• Blaming environment syntax mixing (both styles valid)
• Misreading pgdata volume definition
• Overlooking unquoted multi-word command

5. You want to set up a development environment with a web app and a database using Docker Compose. The web app needs live code updates from your host machine, and the database should persist data between restarts. Which docker-compose.yml configuration correctly achieves this?

hard

A. services:
web:
image: mywebapp
volumes:
- ./code:/app
ports:
- "3000:3000"
db:
image: mysql
environment:
MYSQL_ROOT_PASSWORD: rootpass
volumes:
- dbdata:/var/lib/mysql
volumes:
dbdata:

B. services:
web:
image: mywebapp
ports:
- "3000:3000"
db:
image: mysql
environment:
MYSQL_ROOT_PASSWORD: rootpass
volumes:
dbdata:
driver: local

C. services:
web:
image: mywebapp
volumes:
- /app:/code
ports:
- "3000:3000"
db:
image: mysql
environment:
MYSQL_ROOT_PASSWORD: rootpass
volumes:
- dbdata:/var/lib/mysql
volumes:
dbdata:

D. services:
web:
image: mywebapp
volumes:
- ./code:/app
ports:
- "3000:3000"
db:
image: mysql
environment:
MYSQL_ROOT_PASSWORD: rootpass

Solution

1. Step 1: Ensure live code updates for web app

   Mount host folder ./code to container /app using volumes for live updates.

2. Step 2: Ensure database data persistence

   Use a named volume (dbdata) mounted to /var/lib/mysql to keep data between restarts.

3. Step 3: Check ports and environment

   Expose port 3000 for web and set MYSQL_ROOT_PASSWORD for db environment.

4. Final Answer:

   Configuration with volumes for web and named volume for db -> Option A

5. Quick Check:

   Volumes for live code and persistent db = services: web: image: mywebapp volumes: - ./code:/app ports: - "3000:3000" db: image: mysql environment: MYSQL_ROOT_PASSWORD: rootpass volumes: - dbdata:/var/lib/mysql volumes: dbdata: [OK]

Hint: Use volumes for code and named volume for DB persistence [OK]

Common Mistakes:

• Not mounting host code folder for live updates
• Missing volume for database persistence
• Incorrect volume paths or missing volumes section