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.