docker compose volumes example

Aceder Authors

2 min read

·

13-11-2024

79

0

Share

Unlocking Data Persistence: A Docker Compose Volumes Example

Docker Compose simplifies the process of managing multi-container applications, but what about data? Data within containers is ephemeral by default, meaning it disappears when the container stops. This can be problematic for applications requiring persistent data storage, such as databases or file servers.

Enter Docker Compose volumes, a powerful tool to address this challenge. Volumes provide a dedicated storage location external to the container, ensuring data persistence even after the container is removed.

Let's explore how Docker Compose volumes work with a practical example.

Scenario: A Simple Web App with a Database

Imagine a simple web application built with a Node.js backend (using Express) and a PostgreSQL database. We'll use Docker Compose to orchestrate this application, but our goal is to ensure that the database data persists between container restarts.

1. Define the Services:

Start by defining the services in a docker-compose.yml file. Here's a basic example:

version: "3.8"

services:
  web:
    image: node:18-alpine
    ports:
      - "3000:3000"
    volumes:
      - webdata:/app/data
    command: npm start

  db:
    image: postgres:14
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: my_app_db
    volumes:
      - dbdata:/var/lib/postgresql/data

2. The Power of Volumes:

• webdata and dbdata: We define two volumes named webdata and dbdata. These will act as dedicated storage locations outside the containers.
• volumes: directive: The volumes directive under each service connects the defined volume to the specified directory within the container.
• Data Persistence: When the container restarts, the data within these volumes will be preserved, ensuring the database continues to function correctly.

3. Launching the Application:

Now, simply run the following command to launch your application:

docker-compose up -d

This will build and start the containers, with the volumes linked to the appropriate directories. You can now access your web application at http://localhost:3000.

4. The Benefits of Volumes:

• Persistence: Data is preserved across container restarts.
• Data Sharing: Multiple containers can access and modify the same volume data.
• Efficiency: Volumes avoid the need to rebuild containers every time data is modified.
• Flexibility: You can easily back up or migrate volume data.

Beyond the Basics: Advanced Volume Usage

Docker Compose volumes offer even more flexibility. You can:

• Mount named volumes: Define a named volume in the volumes section of your docker-compose.yml file and then link it to services.
• Mount host directories: Use volumes to share data between containers and your host machine.
• Use data-only containers: Dedicated containers designed solely to manage data.

Example: Data Persistence for a Web Application

Consider a more complex scenario:

• Web Server: A web server (e.g., Nginx) serving static content.
• Database: A database (e.g., MySQL) storing application data.
• Web Application: A Node.js application interacting with the database.

In this case, you can use separate volumes for each service to ensure data persistence for the web server files and database information.

Conclusion

Docker Compose volumes are a fundamental tool for managing data in containerized applications. They provide the ability to store data persistently, even when containers are stopped or removed. Understanding volumes empowers you to build robust and scalable applications by ensuring reliable data storage and retrieval.

Remember to explore the advanced features of Docker Compose volumes to optimize your application's data management strategy.