What is Docker Compose and When Do You Use It?
Learn what Docker Compose is, how compose.yml defines multi-container apps, and when to use it versus Kubernetes.
Expected Interview Answer
Docker Compose is a tool for defining and running multi-container applications from a single declarative YAML file, letting you start, stop, and network an entire stack of services with one command instead of manually running separate docker run commands for each container.
A compose.yml (formerly docker-compose.yml) file declares a set of services, each with its image or build context, environment variables, port mappings, volumes, and dependency ordering via depends_on. Running docker compose up reads that file, creates a dedicated bridge network for the project, builds or pulls each service’s image, and starts every container with the correct configuration and connectivity, so services can immediately reach each other by their service name. Compose is primarily intended for local development and testing, or single-host deployments, because it does not provide the self-healing, multi-host scheduling, or rolling-update capabilities of an orchestrator like Kubernetes. It shines for reproducing a full application stack — a web app, a database, a cache, a message queue — with one file that every developer on the team runs identically.
- Defines an entire multi-service stack in one version-controlled file
- Starts all services with correct networking and dependency order via one command
- Gives every developer an identical local environment
- Simplifies local integration testing of interdependent services
AI Mentor Explanation
Docker Compose is like a match-day team sheet that lists every player, their position, and their role, so the whole team takes the field together in the correct formation with one announcement instead of calling each player out individually. The team manager hands over one sheet, and the umpire, scorers, and support staff all fall into place based on it. If a bowler’s role depends on the wicketkeeper already being in position, the sheet encodes that ordering too. One document coordinates the entire XI instead of eleven separate instructions.
Step-by-Step Explanation
Step 1
Author compose.yml
Declare each service with its image/build, ports, environment, volumes, and depends_on ordering.
Step 2
Run docker compose up
Compose creates a project network, builds/pulls images, and starts every declared service.
Step 3
Services discover each other
Each container can reach others by service name over the auto-created bridge network.
Step 4
Tear down cleanly
docker compose down stops and removes containers and the project network in one command.
What Interviewer Expects
- Understanding of Compose as a single-file, multi-container orchestration tool
- Knowledge of key fields: services, image/build, ports, volumes, depends_on
- Awareness that Compose is best for local/dev/single-host use, not production orchestration
- Ability to explain how service discovery works between Compose services
Common Mistakes
- Using Docker Compose as a production orchestrator instead of Kubernetes/Swarm
- Assuming depends_on waits for a service to be ready, not just started
- Forgetting that named volumes in Compose must be declared under the top-level volumes: key
- Hardcoding IPs instead of using Compose service names for inter-service calls
Best Answer (HR Friendly)
“Docker Compose lets us describe our whole application stack — say, an API, a database, and a cache — in a single file, and then bring the entire thing up or down with one command. Every teammate runs the exact same file, so we all get an identical local environment, which saves a lot of the setup friction and 'works on my machine' issues during development.”
Code Example
services:
api:
build: .
ports:
- "8080:8080"
environment:
DATABASE_URL: postgres://db:5432/app
depends_on:
- db
- cache
db:
image: postgres:16
volumes:
- db-data:/var/lib/postgresql/data
cache:
image: redis:7
volumes:
db-data:Follow-up Questions
- How does Compose service discovery work between containers?
- What is the difference between depends_on and a real health check?
- When would you move from Compose to Kubernetes for a project?
- How do you override compose.yml settings for different environments?
MCQ Practice
1. What is the primary purpose of Docker Compose?
Compose declares a full multi-service application stack in one file and starts it with a single command.
2. How do services in the same Compose file typically reach each other?
Compose creates a dedicated network per project, and services resolve each other by service name automatically.
3. What is a key limitation of Docker Compose compared to Kubernetes?
Compose is best suited to local/single-host use and lacks the orchestration features of a system like Kubernetes.
Flash Cards
What is Docker Compose? — A tool to define and run multi-container applications from one declarative YAML file.
What command starts all services? — docker compose up.
How do services find each other? — By service name over the Compose-created project network.
Best use case for Compose? — Local development, testing, and single-host deployments — not production-scale orchestration.