Notes taken by Horeb S.

Links

🔗 Link of video

Table of contents

What is Docker Compose and why do we need it ?

Previously, we learned how to run individual Docker containers for different services :

• a PostgreSQL database container
• a pgAdmin web interface container
• a Python script for data ingestion

However, managing multiple containers separately can become cumbersome and error-prone. Docker Compose solves this problem by allowing us to define and run multi-container Docker applications using a single YAML file.

This simplifies the deployment process and ensures that all our containers work together as a cohesive unit. With Docker Compose, we can define container configurations, network settings, and dependencies in a declarative way, making our setup more maintainable and reproducible.

In the following sections, we'll explore how to create a Docker Compose configuration that orchestrates our PostgreSQL database and pgAdmin containers, making them work together seamlessly. We'll also look at best practices for managing environment variables and network configurations.

Configuring and running Docker-Compose

First of all, we need to install docker-compose.

🔗 Link to the installation tutorial

The elements we generally have in a Docker-compose yaml file are :

• Version specification - defines which version of Docker Compose syntax to use
• Services - the containers that make up our application
• Networks - how containers communicate with each other