Why advanced Compose features matter in Docker - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use Docker Compose override files?

Docker Compose allows using multiple files like docker-compose.yml and docker-compose.override.yml. What is the main benefit of using override files?

A They let you change or add service settings without modifying the original compose file.

B They automatically update Docker images to the latest version.

C They enable running Compose commands without Docker installed.

D They convert Compose files into Kubernetes manifests.

💡 Hint

Think about how you can keep your base setup safe while customizing for different environments.

Override files let you customize or extend your base Compose setup without changing the original file. This helps keep your main configuration clean and reusable.

💻 Command Output

intermediate

Output of 'docker-compose config' with multiple files

Given these two Compose files:

docker-compose.yml:
version: '3'
services:
  web:
    image: nginx
    ports:
      - "80:80"

docker-compose.override.yml:
version: '3'
services:
  web:
    environment:
      - DEBUG=true

What is the output of docker-compose -f docker-compose.yml -f docker-compose.override.yml config?

A A warning about conflicting versions and no output.

B An error because multiple files cannot be used with the config command.

C Only the base file content without environment variables.

D A combined configuration showing the web service with image nginx, port 80:80, and environment DEBUG=true.

💡 Hint

Think about how Compose merges multiple files.

The config command merges all specified Compose files and shows the final configuration. Here, the override adds the environment variable to the web service.

🔀 Workflow

advanced

Using profiles to control service startup

You want to start only a subset of services defined in your Compose file based on the environment. Which Compose feature helps you do this?

A Profiles allow grouping services and starting only those groups with <code>--profile</code> option.

B Using multiple Compose files with <code>-f</code> to exclude services.

C Manually commenting out services in the Compose file before running.

D Setting environment variables inside the Compose file to disable services.

💡 Hint

Think about a way to tag services and choose which tags to run.

Profiles let you label services and start only those labeled with the selected profile using docker-compose --profile. This avoids editing files or using multiple files.

❓ Troubleshoot

advanced

Why does 'depends_on' not wait for service readiness?

You use depends_on in your Compose file to start services in order. However, sometimes your app fails because the dependency is not ready. Why?

A The dependency service must be manually started before the dependent service.

B <code>depends_on</code> only waits for container start, not for the service inside to be ready.

C Docker Compose does not support <code>depends_on</code> in version 3 files.

D <code>depends_on</code> requires a special flag to wait for readiness that is missing.

💡 Hint

Think about the difference between a container running and the app inside being ready.

depends_on ensures containers start in order but does not check if the service inside is ready to accept connections. You need healthchecks or wait scripts for that.

✅ Best Practice

expert

Why use extension fields (&) in Compose files?

In Docker Compose, what is the main advantage of using YAML anchors and extension fields (using & and *)?

A They automatically convert Compose files to Kubernetes YAML.

B They enable running Compose files faster by caching repeated sections.

C They let you reuse and share configuration snippets to avoid repetition and errors.

D They allow environment variables to be encrypted inside the Compose file.

💡 Hint

Think about how you avoid copying the same text multiple times.

YAML anchors let you define a block once and reuse it multiple times with *. This reduces duplication and mistakes in Compose files.