Compose profiles for selective services in Docker - Step-by-Step Execution

Process Flow - Compose profiles for selective services

Define services in docker-compose.yml

↓

Assign profiles to services

↓

Run docker-compose with profiles

↓

Only services in active profiles start

↓

Other services remain stopped

This flow shows how services are defined with profiles and how running with specific profiles starts only those services.

Execution Sample

Docker

services:
  web:
    image: nginx
    profiles: ["frontend"]
  db:
    image: postgres
    profiles: ["backend"]

Defines two services with different profiles: 'web' in 'frontend' and 'db' in 'backend'.

Process Table

Step	Command	Active Profiles	Services Started	Services Skipped
1	docker-compose up --profile frontend	frontend	web	db
2	docker-compose up --profile backend	backend	db	web
3	docker-compose up --profile frontend --profile backend	frontend, backend	web, db	none
4	docker-compose up	none (default)	none (services with profiles)	web, db

💡 Execution stops after services start according to active profiles or default behavior.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
Active Profiles	none	frontend	backend	frontend, backend	none
Services Started	none	web	db	web, db	none (no unprofiled services)

Key Moments - 2 Insights

Why does 'docker-compose up' without profiles start no services here?

Because both services have profiles assigned, and no default profile is active, so no service matches to start (see execution_table row 4).

Can multiple profiles be active at once?

Yes, as shown in execution_table row 3, running with multiple profiles starts all services assigned to any of those profiles.

Visual Quiz - 3 Questions

Look at the execution table, which services start when running 'docker-compose up --profile backend'?

A db only

B web only

C web and db

D none

💡 Hint

Check execution_table row 2 under 'Services Started'

At which step do both 'web' and 'db' services start together?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

See execution_table row 3 for services started with multiple profiles

If the 'db' service had no profile, what would happen at step 4 when running 'docker-compose up'?

A Only 'web' starts

B 'db' starts, 'web' does not

C Both 'web' and 'db' start

D No services start

💡 Hint

Services without profiles start by default when no profile is specified (see explanation in key_moments)

Concept Snapshot

Compose profiles let you group services.
Assign profiles in docker-compose.yml under each service.
Run with --profile to start only those services.
Multiple profiles can be active together.
Services without profiles start only if no profile is specified.

Full Transcript

In Docker Compose, you can assign profiles to services to control which ones start. When you run 'docker-compose up' with a profile, only services in that profile start. If you run with multiple profiles, all services in those profiles start. Services without profiles start only if you run without any profile specified. This helps run selective services easily.

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