Creating and managing volumes in Docker - Practice Exercises

Challenge - 5 Problems

💻 Command Output

intermediate

Volume Creation Command Output

What is the output of the command docker volume create mydata when run on a system with no existing volume named mydata?

Docker

docker volume create mydata

A Error: volume mydata already exists

B Created volume with ID abc123

C mydata

D No output

💡 Hint

The command returns the name of the created volume if successful.

The docker volume create command outputs the name of the newly created volume. If the volume does not exist, it creates it and prints its name.

❓ Troubleshoot

intermediate

Volume Removal Error Diagnosis

You run docker volume rm mydata but get the error: Error: volume is in use - [container_id]. What is the most likely cause?

A The volume is currently attached to a running container.

B The volume does not exist on the system.

C Docker daemon is not running.

D The volume is corrupted and cannot be removed.

💡 Hint

Volumes cannot be removed if they are used by containers.

Docker prevents removal of volumes that are currently used by containers to avoid data loss or container failure.

❓ Configuration

advanced

Docker Compose Volume Configuration

In a docker-compose.yml file, which volume configuration correctly mounts a named volume dbdata to /var/lib/mysql inside the container?

Docker

version: '3.8'
services:
  db:
    image: mysql
    volumes:

A - dbdata:/var/lib/mysql

B - /var/lib/mysql:dbdata

C

- type: bind
  source: dbdata
  target: /var/lib/mysql

D

- type: volume
  source: dbdata
  target: /var/lib/mysql

💡 Hint

Use the long syntax for named volumes with type volume.

Option D uses the correct long syntax for named volumes in Docker Compose, specifying type, source, and target correctly.

🔀 Workflow

advanced

Volume Backup and Restore Workflow

Which sequence of commands correctly backs up a Docker volume named mydata to a tar file and then restores it?

A docker volume export mydata > mydata.tar.gz && docker volume import mydata.tar.gz mydata

B docker run --rm -v mydata:/data -v $(pwd):/backup busybox tar czf /backup/mydata.tar.gz /data && docker run --rm -v mydata:/data -v $(pwd):/backup busybox tar xzf /backup/mydata.tar.gz -C /data

C docker cp mydata:/ /backup/mydata.tar.gz && docker cp /backup/mydata.tar.gz mydata:/

D docker save mydata > mydata.tar.gz && docker load mydata.tar.gz

💡 Hint

Use a temporary container to access volume data for backup and restore.

Option B uses a temporary container with the volume mounted to create and extract a tar archive for backup and restore.

✅ Best Practice

expert

Choosing Volume Types for Persistent Data

Which statement best describes when to use Docker named volumes instead of bind mounts for persistent data?

A Use named volumes when you want Docker to manage the storage location and lifecycle of data independently from the host filesystem.

B Use named volumes only when you need to share data between containers on different hosts.

C Use bind mounts when you want Docker to manage data storage automatically without host interference.

D Use bind mounts to store data inside Docker’s internal volume storage area.

💡 Hint

Think about who controls the data location and lifecycle.

Named volumes are managed by Docker and stored in Docker’s storage area, making them portable and easier to manage than bind mounts which directly map host directories.

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