Docker Volumes vs Bind Mounts (Step-by-Step Guide) 🐳

Jhoan Sebastian Rojas Holguin — Tue, 08 Sep 2026 20:56:49 +0000

Learn Docker data persistence with a practical 5-minute lab comparing Docker Volumes and Bind Mounts.

Docker Data Persistence: Volumes vs Bind Mounts 🧪

By default, Docker containers are ephemeral. If a container stops or gets deleted, any data created inside it vanishes forever.

To prevent data loss, Docker provides two primary mechanisms for data persistence: Docker Volumes and Bind Mounts.

In this practical guide, we will walk through a 5-minute hands-on lab so you can test both approaches directly on your machine.

📊 Quick Comparison Matrix

Feature	Docker Volumes (Volúmenes)	Bind Mounts
Managed By	Docker Engine (`/var/lib/docker/volumes/`)	User / Host OS
Path on Host	Managed automatically by Docker	Explicit path (e.g., `/home/user/app`)
Best For	Production, Databases, Persistent Storage	Local Development, Live Code Reloading
Portability	High (Easy to backup, restore, migrate)	Low (Tied to specific host folder structure)
CLI Example	`-v my_volume:/app`	`-v /host/path:/app`

🧪 Hands-on Lab: Try It Yourself

Follow these step-by-step exercises in your terminal.

🔒 Part 1: Docker Volumes (Best for Production & Databases)

Docker Volumes are completely managed by Docker and isolated from the core host file system.

Step 1: Create a managed volume

docker volume create my_volume

Verify that the volume was created:

docker volume ls

Step 2: Start a container with the volume attached

docker run -d --name app_volume -v my_volume:/app nginx

Step 3: Write data inside the container

docker exec app_volume bash -c "echo 'Persistent data from Volume' > /app/data.txt"

Verify the file exists inside:

docker exec app_volume cat /app/data.txt

Step 4: Simulate a crash / Destroy the container

docker rm -f app_volume

Step 5: Attach the same volume to a NEW container

docker run -d --name app_volume_new -v my_volume:/app nginx

Step 6: Verify data persistence

docker exec app_volume_new cat /app/data.txt

Result: You will see Persistent data from Volume. The data survived the total destruction of the original container!

Cleanup Part 1:

docker rm -f app_volume_new
docker volume rm my_volume

📂 Part 2: Bind Mounts (Best for Local Development)

Bind Mounts directly link a folder on your host machine to a directory inside the container.

Step 1: Create a local directory on your host machine

mkdir -p ~/docker_lab/html
echo "<h1>Hello from Local Host (V1)</h1>" > ~/docker_lab/html/index.html

Step 2: Start an Nginx container using the bind mount

docker run -d --name web_server -v ~/docker_lab/html:/usr/share/nginx/html -p 8080:80 nginx

Step 3: Test access in your browser or terminal

curl http://localhost:8080

Output: <h1>Hello from Local Host (V1)</h1>

Step 4: Edit the file locally on your host machine (no container restart!)

echo "<h1>Live update reflected instantly! (V2)</h1>" > ~/docker_lab/html/index.html

Step 5: Verify immediate change

curl http://localhost:8080

Output: <h1>Live update reflected instantly! (V2)</h1>

Cleanup Part 2:

docker rm -f web_server
rm -rf ~/docker_lab

💡 Summary & Takeaways / Resumen

Use Docker Volumes when you need secure, isolated, and high-performance storage for databases (e.g., PostgreSQL, MySQL, MongoDB) or production services.
Use Bind Mounts when developing code locally so your IDE edits immediately reflect inside the container without rebuilding images.

💬 Discussion

Which persistence method do you use more in your daily workflow? Have you ever lost data due to container recreation? Let's discuss in the comments below! 👇

#docker #devops #backend #learning

DEV Community: Jhoan Sebastian Rojas Holguin