Docker is an amazing tool that is used by many for containerization. Ever wondered what will happen if the container is shutdown or removed? if it does what about the data in the container? Is it recoverable or can we store that data in the storage? so many questions about docker and we have a concept of Docker volumes as a solution.

What Are Docker Volumes? 🤔

Here volume is a simple term, that we can decode first. Volume is something that holds the data. So, we store the data in the form of Volumes.

Let’s consider a scenario where we store couple of files as folder in the application and it accidentally gets deleted & the folder is also deleted. Hence, we store the data somewhere else so that even if data gets deleted in one location, we can access it and use it if we persist. That’s exactly how docker volumes works!!!

A volume allows you to store data independently from containers, ensuring that data persists even if the container is removed or recreated. 🗂️

Why Use Volumes?

Persistence: Volumes store data outside of containers, so even if the container is deleted, the data remains.
Data Sharing: Volumes allow multiple containers to share data, making it easy to share resources.
Backups and Restore: Volumes can be backed up and restored more easily than container file.

Types of Docker Storage 🗄️

Docker has a few ways to store data, but let’s focus on Volumes as they are the most efficient and flexible option for persistent data.

Volumes: Managed by Docker. You create them with Docker commands, and they are stored outside of the container's filesystem.
Bind Mounts: Links to specific files or directories on the host machine. While they offer more control, they can be trickier to manage.
tmpfs Mounts: In-memory storage. This type is for data that doesn’t need to persist, like temporary files.

Volumes vs. Bind Mounts ⚖️

You might wonder—what’s the difference between volumes and bind mounts? Well, here’s a quick comparison:

Feature	Volumes	Bind Mounts
Storage Location	Managed by Docker (stored on host machine)	Specific file or directory on host
Use Case	Best for Docker-managed persistent data	Useful for sharing host files with containers
Portability	Portable across different environments	Less portable (depends on host paths)
Security	More secure and isolated	Less secure, access directly to host files

Here as you can see, Volumes provide more security, portable and flexible to work with.

Basic Docker Volume Commands

Now that we know why volumes are essential, let’s dive into the key commands that will help you use them like a pro!

1. Create a Volume

To create a volume, you simply use the following command:

$ docker volume create my_volume

This creates a volume named my_volume.

🆕 You can check the list of all volumes with:

$ docker volume ls

2. Using a Volume in a Container 📦

When you launch a container, you can attach a volume to it. This makes sure that the data inside the container is stored in the volume.

$ docker run -d -v my_volume:/app/data my_image

Here my_volume is the volume,

and /app/data is the directory inside the container where the volume will be mounted. 🏗️

3. Inspecting Volumes 🔍

You can get detailed information about a specific volume using:

$ docker volume inspect my_volume

This command shows the volume's location on the host system and other useful metadata. 🕵️‍♀️

4. Removing a Volume ❌

If you no longer need a volume, you can remove it with:

$ docker volume rm my_volume

Just a heads up: Docker will only let you remove a volume if it’s not currently in use by any container. 🧹

5. Prune Unused Volumes 🧺

Over time, you might accumulate unused volumes. If you want to clean them up, use:

$ docker volume prune

It removes all volumes that are not currently associated with any container. (Just make sure you don’t need them first! 💀)

Quick Command Recap 📜

docker volume ls → to check the existing volumes
docker ps → to check containers
docker images → to check images
docker volume create my_volume → Create a new volume.
docker run -d -v my_volume:/path/in/container my_image → Attach a volume to a container.
docker volume inspect my_volume → Inspect details of a volume.
docker volume rm my_volume → Remove a volume.
docker volume prune → Remove unused volumes.

Conclusion 🎉

Docker volumes are a game-changer when it comes to handling persistent data in containers. They make sure that your files stick around even after a container shuts down or is removed. Whether you’re storing databases, logs, or shared data between containers, volumes provide a reliable and efficient solution. 🌍

With the right commands and a little know-how, you’ll be a Docker volume expert in no time!

Happy containerizing! 😄🚀

Docker Volumes: simplifying volumes 🐳

Table of contents