Multiple Compose files (override) in Docker - Step-by-Step Execution

Process Flow - Multiple Compose files (override)

Start with base docker-compose.yml

↓

Read override docker-compose.override.yml

↓

Merge override settings into base

↓

Final combined configuration

↓

Run docker-compose with merged config

Docker Compose reads the base file first, then merges settings from the override file, combining them to create the final configuration used to run containers.

Execution Sample

Docker

version: '3.8'
services:
  web:
    image: nginx:alpine
    ports:
      - "80:80"

Base docker-compose.yml defines a web service running nginx on port 80.

Process Table

Step	File Read	Action	Configuration State	Resulting Service Config
1	docker-compose.yml	Load base config	web service with image nginx:alpine and ports 80:80	web: image=nginx:alpine, ports=[80:80]
2	docker-compose.override.yml	Load override config	override web service with environment and ports	web: environment=[DEBUG=1], ports=[8080:80]
3	Merge override into base	Override ports and add environment	web service with image nginx:alpine, ports 8080:80, environment DEBUG=1	web: image=nginx:alpine, ports=[8080:80], environment=[DEBUG=1]
4	Run docker-compose up	Use merged config	Containers start with final config	web container runs nginx with port 8080 mapped and DEBUG=1 env
5	Exit	Process complete	Final config applied	Containers running as expected

💡 All compose files merged; docker-compose runs containers with combined settings.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
web.image	nginx:alpine	nginx:alpine	nginx:alpine	nginx:alpine
web.ports	[80:80]	[8080:80]	[8080:80]	[8080:80]
web.environment	none	[DEBUG=1]	[DEBUG=1]	[DEBUG=1]

Key Moments - 3 Insights

Why does the port mapping change from 80:80 to 8080:80 after merging?

The override file redefines the ports key, replacing the base ports. See execution_table step 3 where ports are overridden.

Does the override file replace or add to the base configuration?

It merges by replacing keys like ports but adds new keys like environment. Step 3 shows ports replaced and environment added.

What happens if a key is only in the base file and not in the override?

That key stays unchanged in the final config. For example, image remains nginx:alpine as override does not change it.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What is the final port mapping for the web service?

A 80:80

B 80:8080

C 8080:80

D No ports mapped

💡 Hint

Check the 'Resulting Service Config' column at step 3 in execution_table.

At which step does the environment variable DEBUG=1 get added to the web service?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Configuration State' column for environment variables in execution_table.

If the override file did not specify ports, what would be the final port mapping?

A No ports mapped

B 80:80

C 8080:80

D Both 80:80 and 8080:80

💡 Hint

Refer to variable_tracker for web.ports values and how override affects them.

Concept Snapshot

Docker Compose reads multiple files in order.
The override file merges into the base.
Keys in override replace or add to base keys.
Final config combines both for container run.
Use 'docker-compose -f base -f override up' to apply.

Full Transcript

Docker Compose uses multiple files to configure containers. First, it reads the base file, then reads the override file. The override file merges its settings into the base, replacing or adding keys. For example, ports can be replaced, and environment variables can be added. The final combined configuration is used to start containers. This lets you customize or extend your setup easily without changing the base file.