Volume vs bind mount decision in Docker - CLI Comparison

Introduction

When running applications in Docker containers, you often need to save data outside the container. Volumes and bind mounts are two ways to do this. Choosing the right one helps keep your data safe and your app working smoothly.

When you want Docker to manage your data storage automatically and keep it isolated from your host system.

When you need to share specific files or folders from your computer directly with a container for development.

When you want to persist database files so they are safe even if the container is deleted.

When you want to edit source code on your computer and see changes immediately inside the container.

When you want to backup or move data easily between different Docker hosts.

Commands

This command creates a Docker volume named 'my-volume' to store data managed by Docker.

Terminal

docker volume create my-volume

Expected Output

my-volume

Runs a container named 'volume-container' using the 'busybox' image. It mounts the Docker volume 'my-volume' inside the container at /app/data to persist data.

Terminal

docker run -d --name volume-container -v my-volume:/app/data busybox sleep 3600

Expected Output

a1b2c3d4e5f67890123456789abcdef0123456789abcdef0123456789abcdef0

→

-d - Run container in background (detached mode)

→

-v - Mount volume or bind mount inside container

Runs a container named 'bind-container' mounting the host folder '/home/user/project' inside the container at /app. This is a bind mount to share files directly.

Terminal

docker run -d --name bind-container -v /home/user/project:/app busybox sleep 3600

Expected Output

b1c2d3e4f567890123456789abcdef0123456789abcdef0123456789abcdef0

→

-d - Run container in background (detached mode)

→

-v - Mount volume or bind mount inside container

Shows details about the Docker volume 'my-volume', including where Docker stores it on the host.

Terminal

docker volume inspect my-volume

Expected Output

[

    {

        "CreatedAt": "2024-06-01T12:00:00Z",

        "Driver": "local",

        "Labels": {},

        "Mountpoint": "/var/lib/docker/volumes/my-volume/_data",

        "Name": "my-volume",

        "Options": {},

        "Scope": "local"

    }

]

Shows detailed information about the 'bind-container', including the bind mount path from the host.

Terminal

docker inspect bind-container

Expected Output

[

    {

        "Id": "b1c2d3e4f567890123456789abcdef0123456789abcdef0123456789abcdef0",

        "Mounts": [

            {

                "Type": "bind",

                "Source": "/home/user/project",

                "Destination": "/app",

                "Mode": "",

                "RW": true,

                "Propagation": "rprivate"

            }

        ]

    }

]

Key Concept

If you remember nothing else from this pattern, remember: use volumes for Docker-managed persistent data and bind mounts to share host files directly with containers.

Common Mistakes

Using a bind mount to store database files directly on the host.

Bind mounts can cause permission and consistency issues with database files because the host and container handle files differently.

Use a Docker volume to store database files for safe and consistent data management.

Expecting changes in a volume to reflect immediately on the host filesystem.

Docker volumes are managed by Docker and do not map directly to visible host folders, so changes are not directly visible on the host.

Use bind mounts if you need to see and edit files directly on the host.

Not creating a volume before using it in a container.

Docker can create volumes automatically, but explicitly creating them helps manage and inspect volumes easily.

Create volumes explicitly with 'docker volume create' before using them.

Summary

Create Docker volumes to store data managed by Docker and keep it isolated from the host.

Use bind mounts to share specific host folders or files directly with containers for development or configuration.

Inspect volumes and containers to verify where data is stored and how it is mounted.

Practice

1. Which Docker storage option should you use if you want Docker to manage persistent data independently of the host system?

easy

A. Use a temporary container filesystem

B. Use a bind mount

C. Use a network file share

D. Use a Docker volume

Solution

1. Step 1: Understand Docker volume purpose

   Docker volumes are designed to store persistent data managed by Docker itself, independent of the host's file system structure.

2. Step 2: Compare with bind mounts

   Bind mounts link host files or folders directly, so Docker does not manage the data lifecycle.

3. Final Answer:

   Use a Docker volume -> Option D

4. Quick Check:

   Docker manages data = Use volume [OK]

Hint: Docker manages data? Choose volume. Host controls? Choose bind mount. [OK]

Common Mistakes:

• Confusing bind mounts as Docker-managed storage
• Using temporary container filesystem for persistent data
• Assuming network file share is a Docker volume

2. Which of the following is the correct syntax to create a Docker container with a bind mount from host folder /home/user/data to container folder /app/data?

easy

A. docker run -v /home/user/data:/app/data myimage

B. docker run --mount type=bind,source=/app/data,target=/home/user/data myimage

C. docker run --bind /home/user/data:/app/data myimage

D. docker run -v /app/data:/home/user/data myimage

Solution

1. Step 1: Recall bind mount syntax with -v

   The correct syntax for bind mounts with -v is -v host_path:container_path. So -v /home/user/data:/app/data is correct.

2. Step 2: Check other options for errors

   docker run --mount type=bind,source=/app/data,target=/home/user/data myimage reverses source and target paths and uses --mount incorrectly. docker run --bind /home/user/data:/app/data myimage uses invalid flag --bind. docker run -v /app/data:/home/user/data myimage reverses host and container paths.

3. Final Answer:

   docker run -v /home/user/data:/app/data myimage -> Option A

4. Quick Check:

   Bind mount syntax = -v host:container [OK]

Hint: Bind mount syntax: -v host_path:container_path [OK]

Common Mistakes:

• Reversing host and container paths
• Using invalid flags like --bind
• Confusing --mount syntax parameters

3. Given the command docker run -v mydata:/data busybox ls /data, what will be the output if mydata volume is empty?

medium

A. Lists files from host /data directory

B. Shows an empty list (no files)

C. Throws an error: volume not found

D. Lists files from busybox image /data directory

Solution

1. Step 1: Understand volume behavior

   The volume mydata is mounted at /data inside the container. If the volume is empty, the container sees an empty directory at /data.

2. Step 2: Check command output

   The ls /data command lists files in the mounted volume. Since it is empty, the output is empty (no files listed).

3. Final Answer:

   Shows an empty list (no files) -> Option B

4. Quick Check:

   Empty volume = empty directory inside container [OK]

Hint: Empty volume means empty folder inside container [OK]

Common Mistakes:

• Assuming volume auto-fills with image files
• Expecting error if volume is empty
• Confusing volume with bind mount behavior

4. You want to edit source code files live on your host and see changes immediately inside the container. You tried docker run -v /app/src busybox but it fails. What is the error and how to fix it?

medium

A. Error: permission denied; fix by running as root

B. Error: volume not found; fix by creating volume first

C. Error: missing container path; fix by adding host:container in -v

D. Error: invalid image; fix by using correct image name

Solution

1. Step 1: Identify syntax error in -v flag

   The command -v /app/src is incomplete. Docker expects -v host_path:container_path or volume_name:container_path.

2. Step 2: Fix by specifying both paths

   To bind mount host folder /app/src into container, use -v /app/src:/app/src or similar.

3. Final Answer:

   Error: missing container path; fix by adding host:container in -v -> Option C

4. Quick Check:

   -v requires host:container paths [OK]

Hint: -v must have host and container paths separated by colon [OK]

Common Mistakes:

• Using only one path in -v flag
• Confusing volume creation with bind mount syntax
• Ignoring error messages about syntax

5. You want to share a configuration file /etc/config.yaml from your host with multiple containers, and you want Docker to manage the data lifecycle. Which approach is best?

hard

A. Create a Docker volume, copy the file into it, then mount the volume in containers

B. Use a bind mount directly from /etc/config.yaml to containers

C. Copy the file into each container image manually

D. Use a network file share mounted inside containers

Solution

1. Step 1: Understand requirement for Docker-managed data

   You want Docker to manage the data lifecycle, so bind mounts (host-managed) are not ideal.

2. Step 2: Use volume and copy file

   Create a Docker volume, copy /etc/config.yaml into it once, then mount this volume into all containers. This centralizes management.

3. Final Answer:

   Create a Docker volume, copy the file into it, then mount the volume in containers -> Option A

4. Quick Check:

   Docker manages data = use volume + copy file [OK]

Hint: For Docker-managed shared data, use volume with copied files [OK]

Common Mistakes:

• Using bind mounts when Docker management is needed
• Copying files into images instead of using volumes
• Assuming network shares are Docker volumes