Trwałość danych dzięki wolumenom

When you run an application inside a Docker container, any data it creates or modifies is, by default, stored within the container's writable layer. This data is called ephemeral.

This means that if the container is stopped, removed, or crashes, all that valuable data is lost! This is a big problem for databases, user uploads, or configuration files that need to stick around.

We need a robust way to store data outside the container's lifecycle.

Docker volumes are the preferred and most efficient way to persist data generated by and used by Docker containers. They are designed to solve the problem of ephemeral data.

• Volumes are managed by Docker itself, making them more robust and portable.
• They live on the host filesystem, but Docker handles their creation, management, and mounting to containers.
• Crucially, volumes are designed to outlive the container that created them, ensuring your data is safe and persistent.

While volumes are the recommended approach, it's good to know the other main method for persistence:

• Volumes: Docker fully manages the lifecycle and location of the data on the host. This is the primary choice for most containerized applications.
• Bind Mounts: You control the exact mount point on the host filesystem. Docker doesn't manage the host data, giving you more control but less portability.

For this lesson, we'll focus on the powerful and flexible Docker volumes!

Before using a volume with a container, you can explicitly create a named volume. This gives you a clear, manageable reference.

Let's create a volume named my-data.

Now, let's run a container and attach our my-data volume to it. We'll mount it to /app/data inside the container using the -v flag.

When the container writes data to /app/data, that data will be saved in the my-data volume, ensuring it persists.

The data written to our volume is now persistent, even if the container stops or is removed. To prove it, let's run a new, temporary container and mount the same volume to it.

Then, we'll read the message.txt file we created earlier. Notice how the data is still there!

It's good practice to keep track of the volumes on your system. You can easily list all Docker volumes using a simple command. This helps you manage your persistent data storage and identify any unused volumes.

When you no longer need a volume, it's important to remove it to free up disk space. Remember, removing a volume permanently deletes all its data!

First, ensure no containers are actively using the volume. You might need to stop and remove any containers attached to it before removing the volume itself.

Containers are designed to be ephemeral. Which of the following commands is the primary way to ensure data created by a Docker container persists even after the container is removed?

Great job! In this lesson, you learned about Docker volumes and why they are crucial for data persistence:

• Container data is ephemeral and typically lost when containers are removed.
• Docker volumes provide a managed, robust way to store data on the host, independent of the container's lifecycle.
• You learned how to create, use, inspect, list, and remove named volumes.

Now your Dockerized applications can keep their important data safe and accessible!