Creating and managing volumes in Docker - Visual Walkthrough

Process Flow - Creating and managing volumes

Start

↓

Create Volume

↓

List Volumes

↓

Use Volume in Container

↓

Inspect Volume

↓

Remove Volume

↓

End

This flow shows how to create a volume, list it, use it in a container, inspect details, and finally remove it.

Execution Sample

Docker

docker volume create myvol
docker volume ls
docker run -d -v myvol:/data busybox sleep 3600
docker volume inspect myvol
docker volume rm myvol

This sequence creates a volume, lists volumes, runs a container using the volume, inspects the volume, and removes it.

Process Table

Step	Command	Action	Result/Output
1	docker volume create myvol	Create a new volume named 'myvol'	myvol
2	docker volume ls	List all volumes	DRIVER VOLUME NAME local myvol
3	docker run -d -v myvol:/data busybox sleep 3600	Run container with volume mounted at /data	Container ID returned, container running in background
4	docker volume inspect myvol	Show details of volume 'myvol'	[{"Name":"myvol","Driver":"local","Mountpoint":"/var/lib/docker/volumes/myvol/_data"}]
5	docker volume rm myvol	Remove volume 'myvol'	Error: volume is in use by container (if container running) OR 'myvol' removed successfully if container stopped
6	docker rm -f <container_id>	Stop and remove container to free volume	Container removed
7	docker volume rm myvol	Remove volume 'myvol' after container removal	myvol

💡 Volume removal succeeds only after container using it is stopped and removed.

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	After Step 7
Volumes	[]	["myvol"]	["myvol"]	["myvol"] or error if container running	[]
Containers	[]	[]	[container running]	[container running]	[]

Key Moments - 2 Insights

Why can't I remove the volume 'myvol' immediately after creating and using it in a container?

Because the volume is still attached to a running container (see step 5 in execution_table). Docker prevents removing volumes in use to avoid data loss. You must stop and remove the container first (step 6) before removing the volume (step 7).

What does the 'docker volume inspect' command show?

It shows detailed information about the volume, including its name, driver type, and where it is stored on the host (step 4). This helps verify the volume exists and where data is kept.

Visual Quiz - 3 Questions

Look at the execution table, what is the output of 'docker volume ls' at step 2?

A DRIVER VOLUME NAME\nlocal myvol

B myvol

C Error: no volumes found

D Container ID

💡 Hint

Check the 'Result/Output' column for step 2 in the execution_table.

At which step does the container start running with the volume attached?

A Step 1

B Step 3

C Step 5

D Step 7

💡 Hint

Look for the 'docker run' command and container running status in the execution_table.

If you try to remove the volume at step 5 while the container is still running, what happens?

A Volume is removed successfully

B Docker shows an error that volume is in use

C Container stops automatically

D Volume is renamed

💡 Hint

See the 'Action' and 'Result/Output' columns at step 5 in the execution_table.

Concept Snapshot

docker volume create <name>  # Create a volume
docker volume ls             # List volumes
docker run -v <vol>:/path   # Use volume in container
docker volume inspect <name> # Show volume details
docker volume rm <name>     # Remove volume (only if not in use)

Full Transcript

This visual guide shows how to create and manage Docker volumes step-by-step. First, you create a volume with 'docker volume create'. Then, you list volumes to confirm it exists. Next, you run a container that uses the volume by mounting it inside the container. You can inspect the volume to see details like its storage location. Finally, to remove the volume, you must first stop and remove any containers using it, then remove the volume itself. This prevents accidental data loss. The execution table traces each command's action and output, while the variable tracker shows how volumes and containers change state. Key moments clarify why volumes can't be removed while in use and what inspection reveals. The quiz tests understanding of these steps and outputs.

Practice

1. What is the main purpose of Docker volumes?

easy

A. To manage network connections between containers

B. To speed up container startup time

C. To create new containers automatically

D. To store data outside of containers so it is not lost when containers stop

Solution

1. Step 1: Understand what volumes do

   Volumes store data outside the container's writable layer, so data persists even if the container is removed.

2. Step 2: Compare options

   Only To store data outside of containers so it is not lost when containers stop describes this purpose correctly. Other options describe unrelated features.

3. Final Answer:

   To store data outside of containers so it is not lost when containers stop -> Option D

4. Quick Check:

   Volumes keep data safe outside containers = A [OK]

Hint: Volumes keep data safe outside containers [OK]

Common Mistakes:

• Confusing volumes with container networking
• Thinking volumes speed up container start
• Assuming volumes create containers

2. Which command correctly creates a Docker volume named mydata?

easy

A. docker volume new mydata

B. docker volume create mydata

C. docker create volume mydata

D. docker volume add mydata

Solution

1. Step 1: Recall Docker volume creation syntax

   The correct command to create a volume is docker volume create [name].

2. Step 2: Match options to syntax

   Only docker volume create mydata matches the correct syntax exactly.

3. Final Answer:

   docker volume create mydata -> Option B

4. Quick Check:

   Use 'docker volume create' = C [OK]

Hint: Use 'docker volume create' to make volumes [OK]

Common Mistakes:

• Using wrong command order like 'docker create volume'
• Using non-existent commands like 'docker volume new'
• Confusing 'add' with 'create'

3. What is the output of the command docker volume ls after creating two volumes named vol1 and vol2?

medium

A. Lists volumes including vol1 and vol2

B. Lists all containers running

C. Shows detailed info about vol1 only

D. Deletes volumes vol1 and vol2

Solution

1. Step 1: Understand what 'docker volume ls' does

   This command lists all Docker volumes available on the system.

2. Step 2: Interpret the scenario

   After creating volumes vol1 and vol2, the command will list both volumes among others.

3. Final Answer:

   Lists volumes including vol1 and vol2 -> Option A

4. Quick Check:

   'docker volume ls' lists volumes = A [OK]

Hint: 'docker volume ls' shows all volumes [OK]

Common Mistakes:

• Confusing volume list with container list
• Expecting detailed info instead of list
• Thinking it deletes volumes

4. You run docker volume rm myvolume but get an error saying the volume is in use. What should you do to fix this?

medium

A. Restart Docker daemon and try removing again

B. Rename the volume before removing it

C. Stop and remove containers using the volume, then remove the volume

D. Use docker volume create again to overwrite it

Solution

1. Step 1: Understand volume usage error

   Docker prevents removing volumes that are still attached to running or stopped containers.

2. Step 2: Fix by stopping/removing containers

   You must stop and remove containers using the volume before deleting the volume itself.

3. Final Answer:

   Stop and remove containers using the volume, then remove the volume -> Option C

4. Quick Check:

   Remove containers before volumes in use = D [OK]

Hint: Remove containers using volume before deleting volume [OK]

Common Mistakes:

• Trying to rename volume to delete it
• Recreating volume instead of removing
• Restarting Docker daemon without stopping containers

5. You want to create a Docker container that uses a volume named appdata to persist data at /data inside the container. Which command correctly does this?

hard

A. docker run --mount source=appdata,target=/data myimage

B. docker run -v /appdata:/data myimage

C. docker run -v /data appdata myimage

D. docker run --volume /data:appdata myimage

Solution

1. Step 1: Understand volume mounting syntax

   The recommended syntax for mounting a named volume is docker run --mount source=volume_name,target=container_path image. The shorthand -v volume_name:container_path also works, but paths starting with / indicate bind mounts from the host.

2. Step 2: Compare options

   docker run -v /appdata:/data myimage performs a bind mount from the host directory /appdata, not the named volume appdata. docker run --mount source=appdata,target=/data myimage correctly mounts the named volume appdata. The other options (-v /data appdata and --volume /data:appdata) have invalid syntax or incorrect source/target order.

3. Final Answer:

   docker run --mount source=appdata,target=/data myimage -> Option A

4. Quick Check:

   Use --mount source=appdata,target=/data = B [OK]

Hint: Use --mount source=vol,target=path for clarity [OK]

Common Mistakes:

• Mixing volume and container paths order
• Using incorrect flags like --volume with wrong syntax
• Confusing shorthand and long form options