-
- Joined
- Mar 22, 2026
-
- Messages
- 375
-
- Reaction score
- 0
-
- Points
- 0
Docker Compose is an essential tool for defining and running multi-container Docker applications. Instead of managing individual Docker containers, networks, and volumes manually, Compose allows you to describe your entire application stack in a single YAML file, simplifying setup, configuration, and deployment, especially in local development environments.
What is Docker Compose?
At its core, Docker Compose is a tool for running multi-container Docker applications. With Compose, you use a YAML file to configure your application's services. Then, with a single command, you create and start all the services from your configuration. This is incredibly powerful for applications that rely on multiple services, such as a web application with a database, a cache, and a message queue.
Why Use Docker Compose?
1. Reproducibility: Ensures that every developer on a team, and even CI/CD pipelines, runs the exact same environment.
2. Isolation: Each service runs in its own container, isolated from others and the host system.
3. Simplified Management: Start, stop, rebuild, and view logs for all services with simple commands.
4. Rapid Development: Quickly spin up complex environments for testing and development.
Prerequisites
Before diving in, ensure you have Docker Desktop (which includes Docker Compose) installed on your system. You can verify this by running
The
The heart of Docker Compose is the
A typical
*
*
*
*
*
*
Example: A Web App with PostgreSQL
Let's set up a simple Python Flask web application that connects to a PostgreSQL database.
Project Structure:
1.
2.
3.
4.
Running the Application
1. Navigate to the
2. Run
*
*
* The first time, Docker will download the PostgreSQL image and build your Flask app image.
3. Open your browser and go to
4. To see the logs of your services:
5. To stop and remove containers, networks, and volumes defined in the
Key Docker Compose Commands
Docker Compose significantly simplifies the management of multi-container applications, making it an indispensable tool for local development and testing. By mastering its configuration and commands, you can set up complex environments with ease and ensure consistency across your development workflow.
What is Docker Compose?
At its core, Docker Compose is a tool for running multi-container Docker applications. With Compose, you use a YAML file to configure your application's services. Then, with a single command, you create and start all the services from your configuration. This is incredibly powerful for applications that rely on multiple services, such as a web application with a database, a cache, and a message queue.
Why Use Docker Compose?
1. Reproducibility: Ensures that every developer on a team, and even CI/CD pipelines, runs the exact same environment.
2. Isolation: Each service runs in its own container, isolated from others and the host system.
3. Simplified Management: Start, stop, rebuild, and view logs for all services with simple commands.
4. Rapid Development: Quickly spin up complex environments for testing and development.
Prerequisites
Before diving in, ensure you have Docker Desktop (which includes Docker Compose) installed on your system. You can verify this by running
docker --version and docker compose --version (or docker-compose --version for older installations) in your terminal.The
docker-compose.yml FileThe heart of Docker Compose is the
docker-compose.yml (or docker-compose.yaml) file. This file describes your services, networks, and volumes.A typical
docker-compose.yml structure includes:version: Specifies the Compose file format version (e.g.,3.8).services: Defines the application's components. Each service runs in its own container.
image: Specifies the Docker image to use (e.g., nginx:latest, postgres:13).*
build: Specifies a path to a directory containing a Dockerfile for building a custom image.*
ports: Maps host ports to container ports (e.g., "80:80").*
volumes: Mounts host paths or named volumes into containers.*
environment: Sets environment variables inside the container.*
depends_on: Specifies service dependencies (e.g., web app depends on database).*
networks: Attaches services to specific networks.volumes: Defines named volumes for persistent data storage.networks: Defines custom networks for inter-service communication.
Example: A Web App with PostgreSQL
Let's set up a simple Python Flask web application that connects to a PostgreSQL database.
Project Structure:
Code:
my-flask-app/
├── app/
│ ├── app.py
│ └── requirements.txt
├── Dockerfile
└── docker-compose.yml1.
app/requirements.txt:
Code:
Flask
psycopg2-binary2.
app/app.py:
Python:
from flask import Flask
import os
import psycopg2
app = Flask(__name__)
DB_HOST = os.environ.get('DB_HOST', 'db')
DB_NAME = os.environ.get('DB_NAME', 'mydatabase')
DB_USER = os.environ.get('DB_USER', 'user')
DB_PASSWORD = os.environ.get('DB_PASSWORD', 'password')
@app.route('/')
def hello():
try:
conn = psycopg2.connect(host=DB_HOST, database=DB_NAME, user=DB_USER, password=DB_PASSWORD)
cur = conn.cursor()
cur.execute("SELECT 1")
cur.close()
conn.close()
return "Hello from Flask! Connected to PostgreSQL successfully!"
except Exception as e:
return f"Hello from Flask! Failed to connect to PostgreSQL: {e}"
if __name__ == '__main__':
app.run(host='0.0.0.0', port=5000)3.
Dockerfile (for the Flask app):
Code:
# Use an official Python runtime as a parent image
FROM python:3.9-slim-buster
# Set the working directory in the container
WORKDIR /app
# Copy the current directory contents into the container at /app
COPY ./app /app
# Install any needed packages specified in requirements.txt
RUN pip install --no-cache-dir -r requirements.txt
# Make port 5000 available to the world outside this container
EXPOSE 5000
# Run app.py when the container launches
CMD ["python", "app.py"]4.
docker-compose.yml:
YAML:
version: '3.8'
services:
web:
build: .
ports:
- "5000:5000"
environment:
DB_HOST: db
DB_NAME: mydatabase
DB_USER: user
DB_PASSWORD: password
depends_on:
- db
volumes:
- ./app:/app # Mount the local app directory for live changes
db:
image: postgres:13
environment:
POSTGRES_DB: mydatabase
POSTGRES_USER: user
POSTGRES_PASSWORD: password
volumes:
- db_data:/var/lib/postgresql/data # Persistent data volume
volumes:
db_data:Running the Application
1. Navigate to the
my-flask-app directory in your terminal.2. Run
docker compose up -d.*
up: Builds, creates, starts, and attaches to containers for all services.*
-d: Runs containers in detached mode (in the background).* The first time, Docker will download the PostgreSQL image and build your Flask app image.
3. Open your browser and go to
http://localhost:5000. You should see "Hello from Flask! Connected to PostgreSQL successfully!".4. To see the logs of your services:
docker compose logs -f5. To stop and remove containers, networks, and volumes defined in the
docker-compose.yml file: docker compose downKey Docker Compose Commands
docker compose up: Builds, (re)creates, starts, and attaches to containers for a service.docker compose up -d: Starts services in the background.docker compose down: Stops and removes containers, networks, and volumes.docker compose build: Builds or rebuilds services.docker compose ps: Lists containers.docker compose logs [service_name]: Displays log output from services.docker compose exec [service_name] [command]: Executes a command in a running container.
docker compose exec db psql -U user mydatabase to connect to the PostgreSQL shell.Docker Compose significantly simplifies the management of multi-container applications, making it an indispensable tool for local development and testing. By mastering its configuration and commands, you can set up complex environments with ease and ensure consistency across your development workflow.