แอปพลิเคชันหลายคอนเทนเนอร์ด้วย Compose

In real-world applications, you rarely have just one component. Imagine a web application: you need a web server (like Nginx), a backend application (like Python Flask), and a database (like Redis or PostgreSQL).

Each of these components has its own dependencies and configuration. Managing them individually and ensuring they communicate correctly can quickly become complex.

Docker Compose is a tool designed to simplify the process of defining and running multi-container Docker applications.

• You define your entire application's services (containers) in a single YAML file.
• Then, with one simple command, Compose creates and starts all the services for you.
• It's incredibly useful for local development and testing environments.

The heart of Docker Compose is the docker-compose.yml file. This YAML file describes your application's services, networks, and volumes.

It typically starts with a version key, followed by the main services section where you define each container that makes up your application.

Under the services section, you list each component of your application. Each service corresponds to a Docker container.

Key properties for defining a service include:

• image: Specifies the Docker image to use (e.g., nginx:latest).
• build: Provides the path to a directory containing a Dockerfile to build a custom image.
• container_name: An optional, fixed name for your container, making it easier to reference.

You often need to expose your services to the host machine or configure them with environment variables.

• ports: Maps ports from the host to the container (e.g., "8080:80" maps host port 8080 to container port 80).
• environment: Passes environment variables into the container (e.g., DB_HOST: "database").

These settings are crucial for communication and customization.

When you use Docker Compose, it automatically creates a default network for your application. All services defined in your docker-compose.yml file join this network.

This allows services to communicate with each other using their service names as hostnames. For example, a web app service can connect to a database service named redis by simply using redis as the hostname.

Let's build a simple multi-container application: a Python Flask web app that counts how many times it has been visited, storing the count in a Redis database.

This setup clearly shows how a 'web' service can interact with a 'database' service within a single Compose application.

Here's our simple Python Flask application (app.py) and its Dockerfile. The Flask app connects to the redis service, and the Dockerfile packages it all up.

This docker-compose.yml ties everything together. It defines two services: web (our Python app, built from the current directory) and redis (using the official Redis image).

Try running this example!

To start your multi-container application in detached mode (in the background), navigate to the directory containing your docker-compose.yml and supporting files, then run:

To see the running services and their status:

To stop and remove the containers, networks, and volumes created by Compose:

Consider the following docker-compose.yml snippet:

Which statement is TRUE about this configuration?

You've learned how Docker Compose simplifies managing multi-container applications for local development!

• It uses a docker-compose.yml file to define all your services.
• Services can communicate with each other using their service names on a default network.
• Commands like docker compose up and docker compose down manage your entire application stack with ease.

Docker Compose is an essential tool for local development setups involving multiple Docker containers.