How to Use Docker Compose for Multi-Container Applications

1. Tools for Managing Multi-Container Applications

Modern applications rarely run on a single service or container. Instead, they often rely on multiple interconnected services such as web servers, databases, and caches. Managing these components manually can be tedious and error-prone. Thankfully, tools like Docker Compose simplify the process of defining, deploying, and managing multi-container applications.

In this article, we'll explore several tools for managing multi-container environments, walk through building and deploying a project with Docker Compose, and discuss best practices for managing your services efficiently.

1.1 Overview of Podman

Podman, or Pod Manager Tool, is an open-source container engine designed as a drop-in replacement for Docker. It offers a command-line interface to manage containers.

Podman does not require a daemon to run, and it's compatible with systemd, which makes it possible to control containers through systemd units (and run systemd inside the containers).

It helps user organize containers into pods that share the same network and resources.

1.1.1 How to Install Podman

To install Podman on a Linux-based system:

sudo apt update sudo apt install -y podman

For macOS and Windows, you can use the Podman Desktop installer available on the official website.

1.2 Introduction to podman-docker

podman-docker is a compatibility layer that allows you to use Docker CLI commands with Podman. This is especially helpful if you're transitioning from Docker or working with tools that expect Docker commands.

1.2.1 Installing podman-docker

Install podman-docker to enable Docker command compatibility:

sudo apt install -y podman-docker

Once installed, commands like docker run, docker build, or docker-compose will be interpreted by Podman.

1.3 Overview of docker-compose

Docker Compose is a tool for running multi-container Docker applications using a simple YAML configuration file. It allows you to describe all your services, networks, and volumes in a single file and manage them together. Docker Compose supports multiple isolated environments on a single host and variables between them. This means that with this tool, you can recreate containers that undergone changes without altering the multi-container application itself.

1.3.1 How to Install docker-compose

You can install Docker Compose using the official Docker CLI plugin:

sudo apt update sudo apt install docker-compose-plugin

Or for standalone installation (deprecated in favor of the plugin):

sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-
compose-$(uname -s)-$(uname -m)" \ 
-o /usr/local/bin/docker-compose 
sudo chmod +x /usr/local/bin/docker-compose

Verify installation:

docker compose version

Building a Multi-Container Application

Let’s build a simple web application consisting of a web server (Nginx), a backend (Flask), and a database (PostgreSQL).

2.1 Writing the compose.yml File

The compose.yml file (formerly docker-compose.yml) is where all service definitions live.

2.1.1 Defining Services

Each service represents a container. You can specify the image, build context, ports, volumes, and environment variables.

2.1.2 Configuring Networks

Compose allows you to create custom networks so containers can communicate with each other using their service names.

2.1.3 Sample compose.yml File

version: "3.9" 
services: 
   web: 
     build: ./web 
     ports:
- "80:80" 
     depends on:
- backend


backend: build: ./backend 
environment:
- DATABASE_URL=postgres://user:password@db:5432/mydb 
depends_on:
- db


db: 
  image: postgres:15 
  restart: always 
  environment: 
    POSTGRES_DB: mydb 
    POSTGRES_USER: user 
    POSTGRES_PASSWORD: password 
  volumes:
- db_data:/var/lib/postgresql/data
volumes: 
  db_data:

In this setup:

• web is the frontend served by Nginx.
• backend is a Flask API server.
• db is a PostgreSQL container with persistent storage.

2.2 Deploying Multi-Container Applications

Once your compose.yml file is ready, deploy your application using:

docker compose up --build

This command builds the images (if needed) and starts all services. You can stop the application with:

docker compose down

To run the services in the background:

docker compose up -d

Managing a Multi-Container Application

Docker Compose also makes it easy to manage your services. There are possibilities for:

• Scaling services:

docker compose up -d --scale backend=3

This runs three instances of the backend service (useful for load balancing).

• Viewing logs:

docker compose logs -f

• Inspecting service health:

docker compose ps

• Rebuilding images:

docker compose build

• Running one-off commands:

docker compose exec backend flask db upgrade

Docker Compose lets you manage your application lifecycle in a predictable and repeatable way.

With Docker Compose, managing multi-container applications becomes much easier, especially when dealing with environments that require consistent setup and teardown. Whether you're building locally or preparing for production, Compose allows you to define your entire app architecture in a single file and keep everything under control.

Legal Information

Docker is a trademark of Docker, Inc. Podman is an open-source project maintained by Red Hat and others. All software mentioned is subject to its respective open-source licenses.

When deploying applications to production environments, ensure you comply with licensing requirements for all images and dependencies you use.