Volume vs bind mount decision in Docker - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Choosing between Docker volume and bind mount for persistent data

You want to store database data persistently in Docker. Which option best explains when to use a Docker volume instead of a bind mount?

A Use a Docker volume when you want Docker to manage the data storage location and ensure portability across different hosts.

B Use a Docker volume only if you want to directly edit files on the host machine from inside the container.

C Use a bind mount when you want Docker to manage the data storage and isolate it from the host filesystem.

D Use a bind mount when you want Docker to automatically backup the data to the cloud.

💡 Hint

Think about who controls the data location and portability.

Docker volumes are managed by Docker and stored in a Docker-controlled location, making them portable and easier to backup. Bind mounts link directly to host directories, which can be less portable and more dependent on host paths.

💻 Command Output

intermediate

Output of Docker volume inspect command

What is the output type of the command docker volume inspect my_volume?

Docker

docker volume inspect my_volume

A An error message saying the volume does not exist, even if it does.

B A JSON array with detailed information about the volume, including mountpoint and driver.

C A plain text list of files inside the volume.

D A simple string showing only the volume name.

💡 Hint

Think about what 'inspect' commands usually return in Docker.

The docker volume inspect command returns detailed information about the volume in JSON format, including its mountpoint and driver details.

🔀 Workflow

advanced

Correct order to create and use a Docker volume in a container

Arrange the steps in the correct order to create a Docker volume and use it in a container.

A 1,3,2,4

B 3,1,2,4

C 1,2,3,4

D 3,2,1,4

💡 Hint

Think about listing volumes before and after creation, and when to remove.

First, create the volume, then list volumes to see it, run the container using it, and finally remove the volume when no longer needed.

❓ Troubleshoot

advanced

Troubleshooting permission issues with bind mounts

You mounted a host directory into a container using a bind mount, but the container process cannot write to the directory. What is the most likely cause?

A Docker volumes never have permission issues, so the problem is with the container image.

B The container must be restarted twice to apply bind mount permissions.

C Bind mounts automatically change permissions to allow container writes.

D The host directory permissions do not allow the container user to write to it.

💡 Hint

Consider how host filesystem permissions affect bind mounts.

Bind mounts use the host directory directly, so if the host directory permissions do not allow writing by the container user, the container cannot write to it.

✅ Best Practice

expert

Best practice for sharing configuration files between host and container

You want to share configuration files between your host and a Docker container, allowing live edits on the host to reflect immediately inside the container. Which is the best approach?

A Bake the configuration files into the container image and rebuild the image on every change.

B Use a Docker volume to store the configuration files and copy them manually when changed.

C Use a bind mount to link the host configuration directory to the container path.

D Use a Docker secret to store configuration files for live editing.

💡 Hint

Think about live updates and direct file access.

Bind mounts allow the container to access the exact files on the host, so changes on the host are immediately visible inside the container without rebuilding or copying.