Docker Volumes and Persistent Storage

# CHAPTER 6

Docker Volumes and Persistent Storage #

1. Introduction #

2. Learning Objectives #

• Understand the ephemeral nature of container file systems.

• Define what a Docker Volume is and how it persists data.

• Differentiate between Named Volumes and Bind Mounts.

• Mount a local directory into a container for live development.

• Persist database records using a Named Volume.

3. Beginner-Friendly Explanation #

• Without Volumes: You buy groceries and put them in the hotel room's mini-fridge. When your stay is over, you check out, the cleaning staff wipes the room completely clean, and your groceries are thrown in the trash.

• Bind Mount: You bring a magical portal backpack. You attach the portal to the hotel mini-fridge. The portal connects directly to your refrigerator back at your actual house. Anything you put in the hotel fridge is instantly teleported to your home. When you check out of the hotel, the food is safe at your house!

• Named Volume: You rent a permanent, locked storage locker down in the hotel basement. When you check out of Room 101, the locker remains safe. Next week, you check into Room 505 and ask the front desk to connect your room to that exact same storage locker.

4. Bind Mounts (For Live Development) #

The CLI Command (using -v):

docker run -v /Users/john/my-project:/var/www/html nginx

*(Format is -v <Host_Laptop_Path>:<Container_Internal_Path>)*

5. Named Volumes (For Production Databases) #

The CLI Command:

docker run -v db-data:/var/lib/mysql mysql

6. Mini Project: Persist MySQL Data #

Step-by-Step Tutorial:

1. 1. Open your terminal. Let's run a MySQL container and attach a Named Volume to its critical data folder.

docker run -d \
  --name my-database \
  -e MYSQL_ROOT_PASSWORD=secret \
  -v mysql-data:/var/lib/mysql \
  mysql:8.0

*(Notice the -e flag sets an Environment Variable for the password, and -v creates the Named Volume).*

1. 2. Log into the database container:

docker exec -it my-database mysql -u root -p

*(Type secret when prompted for the password).*

1. 3. Inside the MySQL prompt, create some data:

CREATE DATABASE testdb;
SHOW DATABASES;
exit

1. 4. The Catastrophe: Let's completely destroy the container!

docker stop my-database
docker rm my-database

*Oh no! Is testdb gone?*

1. 5. Let's launch a brand new, completely fresh MySQL container, but attach the *exact same* Volume name:

docker run -d \
  --name new-database \
  -e MYSQL_ROOT_PASSWORD=secret \
  -v mysql-data:/var/lib/mysql \
  mysql:8.0

1. 6. Log into the new database and check:

docker exec -it new-database mysql -u root -p

Type SHOW DATABASES;. You will see testdb is still there! The Named Volume successfully shielded your data from the container's destruction.

7. Managing Volumes #

• List Volumes: docker volume ls

• Inspect Volume: docker volume inspect mysql-data

• Delete Volume: docker volume rm mysql-data (Warning: This permanently deletes your data!)

8. Best Practices #

• Never Use Bind Mounts for Databases in Production: Bind mounts rely on the specific file system and permission structure of the host operating system (Windows vs Mac vs Linux). This causes massive permission errors with databases. Always use Docker-managed Named Volumes for database persistence.

9. Common Mistakes #

• The Empty Folder Override: If you create a Bind Mount mapping an *empty* folder on your laptop to a folder inside the container that already contains files, your laptop's empty folder will "overwrite" and hide the container's files! This often causes containers to crash on startup because they suddenly can't find their own configuration files.

10. Exercises #

1. 1. Contrast a Bind Mount with a Named Volume. In what scenario is a Bind Mount highly preferred?

1. 2. If a Docker container running PostgreSQL is forcefully removed (docker rm -f), what happens to the data if the container was utilizing a Named Volume?

11. FAQs #

12. Interview Questions #

• Q: Explain the architectural necessity of Docker Volumes. Provide a scenario demonstrating how deploying a stateful application (like a database) without a volume would result in critical failure.

• Q: A developer wants to see live changes to their HTML/CSS code reflected immediately in their browser without having to run docker build every time they click save. How would you configure their container to achieve this workflow?

13. Summary #

14. Next Chapter Recommendation #