Compose profiles for selective services in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of docker-compose with profile enabled

Given the following docker-compose.yml snippet, what will be the output of docker-compose --profile debug ps?

Docker

version: '3.9'
services:
  app:
    image: alpine
    command: sleep 1000
  debug:
    image: busybox
    command: sleep 1000
    profiles:
      - debug

A Lists both 'app' and 'debug' containers running

B Lists only 'app' container running

C Lists only 'debug' container running

D No containers are listed

💡 Hint

Profiles enable selective service activation; using --profile debug activates services tagged with 'debug' plus those without any profile.

When you run docker-compose --profile debug up, it starts all services without a profile plus those with the 'debug' profile. So both 'app' and 'debug' services run.

❓ Configuration

intermediate

Enable a service only with a specific profile

Which of the following docker-compose.yml service definitions correctly enables the service monitor only when the profile monitoring is active?

A

monitor:
  image: prom/prometheus
  profiles:
    monitoring: true

B

monitor:
  image: prom/prometheus
  profiles:
    - monitoring

C

monitor:
  image: prom/prometheus
  profiles: monitoring

D

monitor:
  image: prom/prometheus
  profile: monitoring

💡 Hint

Profiles are defined as a list under the key 'profiles'.

The correct syntax uses the key profiles with a list of profile names. Option B correctly uses a list with one item 'monitoring'.

❓ Troubleshoot

advanced

Why does a service not start with a profile?

You have a service defined with a profile 'test'. You run docker-compose up without specifying any profile. Why does the service not start?

A The service requires environment variables to start

B The service image is missing, so it cannot start

C The service is disabled by default in docker-compose version 3.9

D Services with profiles only start if the profile is explicitly enabled with --profile

💡 Hint

Profiles control which services start by default.

Services tagged with a profile only start when that profile is enabled explicitly using --profile. Running docker-compose up without profiles starts only services without any profile.

🔀 Workflow

advanced

Selective service start with multiple profiles

Given this docker-compose.yml snippet, which services will start when running docker-compose --profile frontend --profile debug up?

Docker

version: '3.9'
services:
  backend:
    image: backend:latest
  frontend:
    image: frontend:latest
    profiles:
      - frontend
  debug:
    image: debug:latest
    profiles:
      - debug

A Only frontend service

B Only frontend and debug services

C backend, frontend, and debug services

D Only backend service

💡 Hint

Services without profiles always start unless profiles restrict them.

Services without profiles (backend) always start. Services with profiles start only if their profile is enabled. Here, both 'frontend' and 'debug' profiles are enabled, so all three services start.

✅ Best Practice

expert

Best practice for using profiles in production

Which is the best practice when using Docker Compose profiles to manage selective services in a production environment?

A Use profiles to separate optional services like monitoring or debugging, enabling only needed profiles in production

B Define all services without profiles and start only needed ones manually

C Use profiles to disable core services in production to save resources

D Avoid using profiles and rely on multiple compose files for service selection

💡 Hint

Profiles help manage optional services cleanly.

Profiles are designed to enable optional services like monitoring or debugging only when needed. This keeps production environments clean and efficient.

Practice

1. What is the main purpose of using profiles in a Docker Compose file?

easy

A. To define environment variables for all services

B. To specify the Docker image version for services

C. To selectively start specific services based on the active profile

D. To set network configurations for containers

Solution

1. Step 1: Understand the role of profiles in Docker Compose

   Profiles allow you to group services so you can start only those you want by activating a profile.

2. Step 2: Compare with other options

   Environment variables, image versions, and network settings are configured differently, not via profiles.

3. Final Answer:

   To selectively start specific services based on the active profile -> Option C

4. Quick Check:

   Profiles control which services run [OK]

Hint: Profiles control service startup groups in Compose [OK]

Common Mistakes:

• Confusing profiles with environment variables
• Thinking profiles set image versions
• Assuming profiles configure networks

2. Which of the following is the correct syntax to assign a service to a profile named debug in a Docker Compose file?

easy

A. profile: [debug]

B. profiles: [debug]

C. profiles: debug

D. profile: debug

Solution

1. Step 1: Recall the correct key and format for profiles

   The key is profiles (plural) and it expects a list of profile names.

2. Step 2: Validate the syntax

   Using YAML list syntax, profiles: [debug] is correct. Other options use singular or wrong types.

3. Final Answer:

   profiles: [debug] -> Option B

4. Quick Check:

   Profiles key is plural and uses list syntax [OK]

Hint: Use plural 'profiles' with a list for service assignment [OK]

Common Mistakes:

• Using singular 'profile' instead of 'profiles'
• Not using list syntax for profiles
• Assigning profile as a string without brackets

3. Given this Compose snippet:

services:
  web:
    image: nginx
  debug:
    image: busybox
    profiles: [debug]

What happens when you run docker compose up without any profile?

medium

A. Only the web service starts

B. Both web and debug services start

C. Only the debug service starts

D. No services start

Solution

1. Step 1: Identify which services have profiles

   The debug service is assigned to the profile 'debug', web has no profile.

2. Step 2: Understand default behavior without profile

   Without specifying a profile, only services without profiles start.

3. Final Answer:

   Only the web service starts -> Option A

4. Quick Check:

   Services without profiles start by default [OK]

Hint: Without profile flag, only services without profiles run [OK]

Common Mistakes:

• Assuming all services start by default
• Thinking profile services start without activation
• Confusing service names with profile names

4. You have this Compose file snippet:

services:
  app:
    image: myapp
    profiles: [prod]
  test:
    image: mytest
    profiles: [test]

You run docker compose --profile prod up but the app service does not start. What is the likely issue?

medium

A. The profile name is misspelled in the command

B. The app service must not have any profile to start

C. You must run docker compose up without profiles to start services

D. The Compose file syntax is invalid

Solution

1. Step 1: Check profile names in Compose and command

   The service uses profile 'prod'. If the command misspells it, the service won't start.

2. Step 2: Understand profile activation

   Only services matching the activated profile start. If the profile name is wrong, no matching service starts.

3. Final Answer:

   The profile name is misspelled in the command -> Option A

4. Quick Check:

   Profile names must match exactly [OK]

Hint: Check exact profile spelling in command and Compose file [OK]

Common Mistakes:

• Assuming services without profiles start with any profile
• Thinking Compose file syntax error causes this
• Believing profiles are optional for service start

5. You want to start only the db and cache services using profiles. Your Compose file has:

services:
  db:
    image: postgres
    profiles: [backend]
  cache:
    image: redis
    profiles: [backend]
  frontend:
    image: nginx
    profiles: [frontend]

Which command will start only the db and cache services?

hard

A. docker compose up

B. docker compose --profile frontend up

C. docker compose --profile db cache up

D. docker compose --profile backend up

Solution

1. Step 1: Identify profiles assigned to db and cache

   Both db and cache are under the 'backend' profile.

2. Step 2: Use the correct command to activate the backend profile

   Running docker compose --profile backend up starts only services in 'backend'.

3. Final Answer:

   docker compose --profile backend up -> Option D

4. Quick Check:

   Activate profile matching services to start them [OK]

Hint: Use --profile with the shared profile name to start grouped services [OK]

Common Mistakes:

• Using profile name not assigned to services
• Running without profile starts no profile services only
• Trying to list services in command instead of profile