Debugging volume mount issues in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Volume mount path error output

What error message will Docker show if you try to mount a host directory that does not exist?

Docker

docker run -v /nonexistent/path:/app busybox ls /app

A Error: No such container: /nonexistent/path

B ls: cannot access '/app': No such file or directory

C Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /nonexistent/path

D Permission denied while accessing /nonexistent/path

💡 Hint

Docker checks if the host path exists before starting the container.

Docker requires the host directory to exist before mounting it. If it doesn't, Docker shows an error about invalid mount config and missing source path.

❓ Troubleshoot

intermediate

Container cannot write to mounted volume

You mounted a host directory into a container, but the container process cannot write files inside it. What is the most likely cause?

A The host directory has read-only permissions for the container user

B The container image does not have write permissions on /bin

C Docker daemon is running in rootless mode

D The container network is disconnected

💡 Hint

Check the permissions of the host directory and the user inside the container.

If the host directory is owned by root and has no write permission for others, the container user cannot write to it. This is a common cause of write failures.

❓ Configuration

advanced

Correct volume mount syntax in docker-compose

Which docker-compose volume syntax correctly mounts the host directory /data into /app/data inside the container with read-write access?

A

volumes:
  - /data:/app/data:rw

B

volumes:
  - /data:/app/data

C

volumes:
  - /app/data:/data

D

volumes:
  - /data:/app/data:ro

💡 Hint

By default, volume mounts are read-write unless specified otherwise.

The syntax '/data:/app/data' mounts the host /data directory into the container path /app/data with read-write access by default. Adding ':rw' is optional but valid.

✅ Best Practice

advanced

Avoiding permission issues with Docker volumes

What is the best practice to avoid permission problems when mounting host directories into Docker containers?

A Disable SELinux or AppArmor on the host

B Run the container as root user to bypass permission checks

C Always mount host directories as read-only

D Use named Docker volumes instead of host directory mounts

💡 Hint

Consider Docker-managed storage to avoid host permission conflicts.

Named Docker volumes are managed by Docker and avoid host permission issues because Docker controls the volume's ownership and permissions. This is a best practice for consistent behavior.

🧠 Conceptual

expert

Understanding volume mount propagation modes

Which volume mount propagation mode allows changes in the container's mounted volume to be reflected back to the host and other containers?

A rshared

B rprivate

C rslave

D private

💡 Hint

Propagation modes control how mount events propagate between host and container.

The 'rshared' propagation mode allows mount and unmount events to propagate both ways between the host and container, enabling changes in the container to be visible on the host and other containers.

Practice

1. What is the main purpose of using volume mounts in Docker?

easy

A. To share files between the host machine and the container

B. To increase the container's CPU usage

C. To change the container's network settings

D. To update the Docker engine version

Solution

1. Step 1: Understand volume mounts

   Volume mounts allow sharing files or folders between your computer (host) and the Docker container.

2. Step 2: Identify the purpose

   This sharing helps containers access or save data on the host, making data persistent or accessible.

3. Final Answer:

   To share files between the host machine and the container -> Option A

4. Quick Check:

   Volume mounts = file sharing [OK]

Hint: Volume mounts connect host and container files [OK]

Common Mistakes:

• Confusing volume mounts with CPU or network settings
• Thinking volume mounts update Docker itself
• Assuming volume mounts only work inside containers

2. Which of the following is the correct syntax to mount a host folder /data to a container folder /app/data using docker run?

easy

A. docker run --mount /data:/app/data image_name

B. docker run -v /app/data:/data image_name

C. docker run -v /data:/app/data image_name

D. docker run -volume /data:/app/data image_name

Solution

1. Step 1: Recall volume mount syntax

   The correct syntax uses -v host_path:container_path to mount volumes.

2. Step 2: Match paths correctly

   The host folder /data should be before the colon, and container folder /app/data after.

3. Final Answer:

   docker run -v /data:/app/data image_name -> Option C

4. Quick Check:

   Host path before colon, container path after [OK]

Hint: Use -v host_path:container_path exactly [OK]

Common Mistakes:

• Swapping host and container paths
• Using incorrect flags like --mount without full syntax
• Typing -volume instead of -v

3. You run this command:
docker run -v /host/data:/container/data busybox ls /container/data
But the output is empty even though /host/data has files. What is the likely cause?

medium

A. The host path /host/data does not exist or is empty

B. The container image busybox does not support volume mounts

C. The container path /container/data is incorrect

D. The Docker daemon is not running

Solution

1. Step 1: Check host path existence

   If the host folder /host/data does not exist or is empty, the container will see nothing.

2. Step 2: Confirm container path and image

   The container path and busybox image support volume mounts, so they are unlikely the issue.

3. Final Answer:

   The host path /host/data does not exist or is empty -> Option A

4. Quick Check:

   Empty mount means host folder missing or empty [OK]

Hint: Check host folder exists and has files [OK]

Common Mistakes:

• Blaming the container image for mount issues
• Assuming container path must exist before mount
• Ignoring host folder permissions or existence

4. You tried to mount a folder with docker run -v /host/folder:/container/folder but got a permission denied error inside the container. What should you check first?

medium

A. If the Docker image supports the mounted folder

B. If the Docker CLI version is up to date

C. If the container folder path is a valid Linux path

D. If the host folder has correct read/write permissions

Solution

1. Step 1: Understand permission errors

   Permission denied usually means the container user cannot access the host folder due to host permissions.

2. Step 2: Verify host folder permissions

   Check if the host folder allows read/write access for Docker or the container user.

3. Final Answer:

   If the host folder has correct read/write permissions -> Option D

4. Quick Check:

   Permission denied = check host folder permissions [OK]

Hint: Check host folder permissions first on errors [OK]

Common Mistakes:

• Assuming container image causes permission errors
• Ignoring host file system permissions
• Updating Docker CLI instead of fixing permissions

5. You want to mount a host folder /data into a container at /app/data but only want the container to read files, not write. Which command correctly sets a read-only volume mount?

hard

A. docker run -v /data:/app/data:rw image_name

B. docker run -v /data:/app/data:ro image_name

C. docker run -v /data:/app/data:read image_name

D. docker run -v /data:/app/data:readonly image_name

Solution

1. Step 1: Recall volume mount options

   Docker uses :ro to mark a volume as read-only and :rw for read-write (default).

2. Step 2: Identify correct option

   Only :ro is valid for read-only; others like :read or :readonly are invalid.

3. Final Answer:

   docker run -v /data:/app/data:ro image_name -> Option B

4. Quick Check:

   Use :ro suffix for read-only mounts [OK]

Hint: Add :ro suffix for read-only mounts [OK]

Common Mistakes:

• Using :rw or invalid suffixes for read-only
• Forgetting the colon before options
• Assuming read-only is default