Why Docker Compose simplifies multi-container apps - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Docker Compose benefits

Which of the following best explains why Docker Compose simplifies managing multi-container applications?

A It automatically converts containers into virtual machines for better isolation.

B It replaces Docker Engine and runs containers faster by using a different runtime.

C It allows defining all containers and their settings in a single YAML file, enabling easy startup and management with one command.

D It requires writing separate scripts for each container to manage their lifecycle.

💡 Hint

Think about how you would start multiple containers together easily.

Docker Compose uses a YAML file to define multiple containers and their settings. This lets you start, stop, and manage all containers with simple commands like docker-compose up.

💻 Command Output

intermediate

Output of docker-compose up command

What is the expected output when running docker-compose up for a valid docker-compose.yml defining two services?

Docker

version: '3'
services:
  web:
    image: nginx
  db:
    image: mysql

A

Starting web ... done
Starting db ... done
Attaching to web, db

B Syntax error in docker-compose.yml at line 2

C

Container web created
Container db created
No output attached

D Error: docker-compose.yml file not found

💡 Hint

Think about what happens when containers start successfully.

When docker-compose up runs successfully, it starts the defined services and attaches to their logs, showing messages like 'Starting web ... done'.

❓ Configuration

advanced

Correct service dependency declaration in Docker Compose

Which docker-compose.yml snippet correctly ensures that the web service starts only after the db service is ready?

A

services:
  web:
    image: nginx
    depends_on:
      - db
  db:
    image: mysql

B

services:
  web:
    image: nginx
    links:
      - db
  db:
    image: mysql

C

services:
  web:
    image: nginx
    wait_for:
      - db
  db:
    image: mysql

D

services:
  web:
    image: nginx
    start_after:
      - db
  db:
    image: mysql

💡 Hint

Look for the official Docker Compose keyword for service dependencies.

The depends_on key tells Docker Compose to start the db service before web. Other keys like links or wait_for are not valid for this purpose.

❓ Troubleshoot

advanced

Diagnosing Docker Compose network issue

You have two services in docker-compose.yml: app and db. The app service cannot connect to db using the service name as hostname. What is the most likely cause?

A The <code>db</code> service image is missing the database software.

B The services are defined under different networks, so they cannot resolve each other by service name.

C Docker Compose does not support service name resolution between containers.

D The <code>app</code> service is missing a volume mount for the database files.

💡 Hint

Think about how Docker Compose handles container networking by default.

By default, Docker Compose creates a single network for all services, allowing them to communicate by service name. If services are on different networks, they cannot resolve each other.

🔀 Workflow

expert

Order of commands to update a multi-container app with Docker Compose

What is the correct order of commands to update the images and restart all services in a Docker Compose multi-container app?

A 2,1,3,4

B 2,3,1,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Pull new images first, then stop old containers, then start updated ones.

First, docker-compose pull updates images. Then docker-compose down stops and removes containers. Next, docker-compose up -d starts containers with new images. Finally, docker-compose ps shows running containers.

Practice

1. What is the main benefit of using Docker Compose for multi-container applications?

easy

A. It allows managing multiple containers with a single configuration file and command.

B. It replaces Docker Engine for running containers.

C. It automatically updates container images without user input.

D. It only works with single-container applications.

Solution

1. Step 1: Understand Docker Compose purpose

   Docker Compose uses one file to define and run multiple containers together easily.

2. Step 2: Compare options

   Options B, C, and D describe incorrect or unrelated features. Only It allows managing multiple containers with a single configuration file and command. correctly states the main benefit.

3. Final Answer:

   It allows managing multiple containers with a single configuration file and command. -> Option A

4. Quick Check:

   Single file + command = easier multi-container management [OK]

Hint: Think: one file controls many containers [OK]

Common Mistakes:

• Confusing Docker Compose with Docker Engine
• Believing Compose updates images automatically
• Thinking Compose works only for one container

2. Which of the following is the correct command to start all services defined in a docker-compose.yml file?

easy

A. docker-compose run

B. docker-compose up

C. docker-compose build

D. docker-compose start-all

Solution

1. Step 1: Identify the command to launch services

   The docker-compose up command starts all containers defined in the compose file.

2. Step 2: Review other commands

   run starts a one-off container, build builds images, and start-all is invalid.

3. Final Answer:

   docker-compose up -> Option B

4. Quick Check:

   Start all services = docker-compose up [OK]

Hint: Use 'up' to launch all services together [OK]

Common Mistakes:

• Using 'run' instead of 'up' to start all containers
• Confusing 'build' with starting containers
• Using a non-existent command like 'start-all'

3. Given this docker-compose.yml snippet:

version: '3'
services:
  web:
    image: nginx
    ports:
      - "8080:80"
  db:
    image: mysql
    environment:
      MYSQL_ROOT_PASSWORD: example

What happens when you run docker-compose up?

medium

A. Only the web service starts, exposing port 80 on 8080.

B. The db service starts but fails due to missing password.

C. Both web and db services start; web is accessible on port 8080.

D. No containers start because the file version is incorrect.

Solution

1. Step 1: Analyze the compose file

   Two services: 'web' with nginx exposing port 8080:80, and 'db' with mysql and a root password set.

2. Step 2: Understand the command effect

   docker-compose up starts all services defined, so both 'web' and 'db' start successfully.

3. Final Answer:

   Both web and db services start; web is accessible on port 8080. -> Option C

4. Quick Check:

   All services start with 'up' if config is valid [OK]

Hint: All services in file start with 'docker-compose up' [OK]

Common Mistakes:

• Thinking only one service starts by default
• Assuming missing environment variables cause failure here
• Believing file version '3' is invalid

4. You wrote a docker-compose.yml but running docker-compose up gives an error: ERROR: yaml.scanner.ScannerError: mapping values are not allowed here. What is the most likely cause?

medium

A. Incorrect indentation or syntax in the YAML file.

B. Docker Compose is not installed on the system.

C. The Docker daemon is not running.

D. The image names are missing in the file.

Solution

1. Step 1: Understand the error message

   The error indicates a YAML syntax problem, usually caused by wrong indentation or misplaced characters.

2. Step 2: Evaluate other options

   Options B and C cause different errors, and missing image names cause different warnings, not YAML syntax errors.

3. Final Answer:

   Incorrect indentation or syntax in the YAML file. -> Option A

4. Quick Check:

   YAML errors = check indentation and syntax [OK]

Hint: YAML errors usually mean bad indentation [OK]

Common Mistakes:

• Assuming Docker Compose is missing when error is YAML
• Thinking Docker daemon status causes YAML errors
• Ignoring indentation rules in YAML files

5. You want to share your multi-container app setup with a teammate. Which Docker Compose feature best helps you do this efficiently?

hard

A. Using Docker Swarm instead of Compose for local development.

B. Running each container manually with separate docker run commands.

C. Building images locally and sending them as tar files.

D. Using a single docker-compose.yml file to define all services and their settings.

Solution

1. Step 1: Identify sharing method for multi-container apps

   A single docker-compose.yml file contains all service definitions and configurations, making sharing easy.

2. Step 2: Compare other options

   Manual docker run commands are error-prone and complex; sending images as tar files is cumbersome; Docker Swarm is for orchestration, not simple sharing.

3. Final Answer:

   Using a single docker-compose.yml file to define all services and their settings. -> Option D

4. Quick Check:

   One file shares whole app setup easily [OK]

Hint: Share one compose file, not many commands [OK]

Common Mistakes:

• Thinking manual commands are easier to share
• Believing image tar files are best for sharing setup
• Confusing Docker Swarm with Compose for local sharing