Storage driver options in Docker - Step-by-Step Execution

Process Flow - Storage driver options

Docker daemon starts

↓

Reads storage driver config

↓

Select storage driver

↓

Initialize driver

↓

Manage container layers

↓

Store container data

↓

Containers run with storage

↓

Docker daemon stops

Docker reads the configured storage driver when it starts, initializes it, and uses it to manage container file layers and data storage.

Execution Sample

Docker

docker info --format '{{.Driver}}'
docker run --rm alpine ls /
docker info --format '{{.DriverStatus}}'

Shows the current storage driver, runs a container, then shows detailed driver status.

Process Table

Step	Command	Action	Output / Result
1	docker info --format '{{.Driver}}'	Check current storage driver	overlay2
2	docker run --rm alpine ls /	Run container and list root directory	bin etc lib proc root sys tmp usr var
3	docker info --format '{{.DriverStatus}}'	Show detailed storage driver status	["Backing Filesystem", "ext4"], ["Supports d_type", "true"], ["Native Overlay Diff", "true"]

💡 Commands complete showing storage driver in use and container filesystem accessed.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
Storage Driver	unknown	overlay2	overlay2	overlay2
Container Filesystem	none	none	mounted and listed	mounted and listed

Key Moments - 3 Insights

Why does Docker need to know the storage driver before running containers?

Docker uses the storage driver to manage how container files and layers are stored and accessed. Without it, containers cannot read or write files properly. See execution_table step 1 and 2.

What does the 'overlay2' driver mean in the output?

'overlay2' is a modern storage driver that uses overlay filesystem technology to efficiently manage container layers. It is shown in execution_table step 1 output.

Why do we run 'docker info --format '{{.DriverStatus}}'' after running a container?

This command shows detailed info about the storage driver capabilities and status, confirming it is working correctly with the container filesystem. See execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution_table step 1, what storage driver is Docker using?

A aufs

B overlay2

C devicemapper

D btrfs

💡 Hint

Check the output column in execution_table step 1.

At which step do we see the container filesystem contents listed?

A Step 1

B Step 3

C Step 2

D None

💡 Hint

Look for the 'ls /' command output in execution_table.

If Docker used 'aufs' instead of 'overlay2', which step output would change?

A Step 1 and Step 3

B Step 2 only

C Step 1 only

D All steps

💡 Hint

Storage driver name appears in step 1 and detailed driver info in step 3.

Concept Snapshot

Docker Storage Driver Options:
- Docker selects a storage driver at daemon start.
- Storage driver manages container file layers.
- Common drivers: overlay2 (modern), aufs, devicemapper.
- Check current driver: docker info --format '{{.Driver}}'
- Detailed status: docker info --format '{{.DriverStatus}}'
- Driver affects container filesystem performance and features.

Full Transcript

When Docker starts, it reads the configured storage driver option. This driver controls how Docker stores and manages container files and layers. For example, the 'overlay2' driver uses overlay filesystem technology to efficiently handle container data. Running 'docker info --format '{{.Driver}}'' shows which driver is active. Running a container like 'docker run --rm alpine ls /' mounts the container filesystem using that driver. Finally, 'docker info --format '{{.DriverStatus}}'' shows detailed info about the driver's capabilities and status. Understanding storage drivers helps troubleshoot container storage and performance issues.

Practice

1. What is the main purpose of a Docker storage driver?

easy

A. To manage how Docker stores container data on disk

B. To control network settings for containers

C. To schedule container start times

D. To monitor container CPU usage

Solution

1. Step 1: Understand Docker storage drivers

   Storage drivers define how Docker saves and manages container data on the host disk.

2. Step 2: Identify the correct function

   Among the options, only managing container data storage matches the role of storage drivers.

3. Final Answer:

   To manage how Docker stores container data on disk -> Option A

4. Quick Check:

   Storage driver = manages container data storage [OK]

Hint: Storage drivers handle container data storage, not networking or CPU [OK]

Common Mistakes:

• Confusing storage drivers with network drivers
• Thinking storage drivers manage container resource limits
• Assuming storage drivers schedule container tasks

2. Which of the following is the correct syntax to specify the storage driver when starting the Docker daemon manually?

easy

A. docker run --storage-driver=overlay2

B. dockerd --storage-driver=overlay2

C. dockerd -storage driver overlay2

D. docker daemon --storage=overlay2

Solution

1. Step 1: Recall Docker daemon start syntax

   The Docker daemon is started with the command 'dockerd' and options use double dashes with hyphens.

2. Step 2: Match correct option format

   dockerd --storage-driver=overlay2 uses 'dockerd --storage-driver=overlay2' which is the correct syntax to set the storage driver.

3. Final Answer:

   dockerd --storage-driver=overlay2 -> Option B

4. Quick Check:

   Daemon start uses 'dockerd --storage-driver' [OK]

Hint: Use 'dockerd --storage-driver=drivername' to set storage driver [OK]

Common Mistakes:

• Using 'docker run' instead of 'dockerd' to set storage driver
• Incorrect flag syntax like '-storage driver'
• Using 'docker daemon' which is deprecated

3. Given the Docker daemon started with dockerd --storage-driver=aufs, what will be the output of docker info | grep 'Storage Driver'?

medium

A. Storage Driver: aufs

B. Storage Driver: btrfs

C. Storage Driver: devicemapper

D. Storage Driver: overlay2

Solution

1. Step 1: Understand the command effect

   The command 'docker info | grep "Storage Driver"' filters Docker info output to show the storage driver in use.

2. Step 2: Match the storage driver set at daemon start

   Since the daemon was started with '--storage-driver=aufs', the output will show 'Storage Driver: aufs'.

3. Final Answer:

   Storage Driver: aufs -> Option A

4. Quick Check:

   Set driver = output driver [OK]

Hint: Output matches the driver set at daemon start [OK]

Common Mistakes:

• Assuming default driver instead of the one set
• Confusing output with other storage drivers
• Not using correct grep syntax

4. You tried to start Docker with dockerd --storage-driver=overlay3 but it failed. What is the most likely reason?

medium

A. The storage driver option requires a space, not an equals sign

B. You need to use 'docker run' instead of 'dockerd'

C. Docker does not support storage drivers on Linux

D. overlay3 is not a valid Docker storage driver

Solution

1. Step 1: Verify valid storage drivers

   Docker supports drivers like overlay2, aufs, devicemapper, but 'overlay3' is not a valid driver.

2. Step 2: Check command usage

   The command 'dockerd --storage-driver=overlay3' is correct syntax, but the driver name is invalid, causing failure.

3. Final Answer:

   overlay3 is not a valid Docker storage driver -> Option D

4. Quick Check:

   Invalid driver name causes failure [OK]

Hint: Check driver name spelling and validity before starting daemon [OK]

Common Mistakes:

• Using invalid or unsupported driver names
• Confusing 'dockerd' with 'docker run'
• Incorrect flag syntax

5. You want to optimize Docker performance on a system with an ext4 filesystem. Which storage driver option should you choose in the Docker daemon configuration file for best compatibility and performance?

hard

A. aufs

B. devicemapper

C. overlay2

D. btrfs

Solution

1. Step 1: Identify filesystem compatibility

   Overlay2 is recommended for ext4 filesystems because it is stable and performs well on ext4.

2. Step 2: Compare other drivers

   Devicemapper is older and less efficient; aufs is deprecated on many systems; btrfs requires btrfs filesystem, not ext4.

3. Final Answer:

   overlay2 -> Option C

4. Quick Check:

   ext4 + overlay2 = best performance [OK]

Hint: Use overlay2 for ext4 filesystem for best Docker performance [OK]

Common Mistakes:

• Choosing btrfs on ext4 filesystem
• Using devicemapper despite better options
• Assuming aufs is always best