Bind mounts for development in Docker - Commands & Configuration

Introduction

When you develop software, you often want your code changes to appear immediately inside a running container without rebuilding it. Bind mounts let you link a folder on your computer directly into the container, so changes happen live.

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

When you need to share configuration files between your host and a container during development.

When you want to avoid rebuilding a container image every time you change source files.

When you want to debug or test code inside a container using your local tools.

When you want to keep your source code outside the container for easier version control.

Commands

This command runs an Nginx container in the background named 'my-dev-container'. The '-v' flag creates a bind mount that links your local folder '/home/user/myapp' to '/app' inside the container. This means any changes you make in '/home/user/myapp' appear immediately inside the container at '/app'.

Terminal

docker run -d --name my-dev-container -v /home/user/myapp:/app nginx:1.25

Expected Output

a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6

→

-d - Run container in detached (background) mode

→

--name - Assign a custom name to the container

→

-v - Create a bind mount between host and container directories

This command lists the files inside the '/app' directory of the running container 'my-dev-container'. It helps verify that your local files are visible inside the container through the bind mount.

Terminal

docker exec -it my-dev-container ls /app

Expected Output

index.html

styles.css

app.js

→

-it - Run the command interactively with a terminal

Stops the running container named 'my-dev-container'. This is useful when you finish your development session.

Terminal

docker stop my-dev-container

Expected Output

my-dev-container

Removes the stopped container named 'my-dev-container' to clean up your system.

Terminal

docker rm my-dev-container

Expected Output

my-dev-container

Key Concept

If you remember nothing else from this pattern, remember: bind mounts link your local folder directly into the container so changes happen live without rebuilding.

Common Mistakes

Using a relative path instead of an absolute path for the bind mount source.

Docker requires an absolute path on the host for bind mounts; relative paths cause errors or unexpected behavior.

Always specify the full absolute path to your local folder, like '/home/user/myapp'.

Not having the local folder exist before running the container with a bind mount.

If the local folder does not exist, Docker may create an empty folder or fail, leading to missing files inside the container.

Create the local folder and add your files before running the container with the bind mount.

Binding a folder with incorrect permissions causing the container to not read or write files.

If the container user lacks permission to access the bind mount folder, your app may fail or behave unexpectedly.

Ensure the folder permissions on your host allow the container user to read/write as needed.

Summary

Use the '-v' flag with 'docker run' to create a bind mount linking a local folder to a container folder.

Verify the bind mount works by listing files inside the container with 'docker exec'.

Stop and remove containers when done to keep your system clean.

Practice

1. What is the main purpose of using bind mounts in Docker during development?

easy

A. To automatically update Docker itself

B. To link files or folders from the host machine directly into the container for live editing

C. To isolate the container completely from the host file system

D. To create a new Docker image from a container

Solution

1. Step 1: Understand bind mounts concept

   Bind mounts connect a folder or file on your computer (host) directly into the container, so changes on the host reflect immediately inside the container.

2. Step 2: Identify the purpose in development

   This allows developers to edit code on their computer and see the changes live inside the container without rebuilding the image.

3. Final Answer:

   To link files or folders from the host machine directly into the container for live editing -> Option B

4. Quick Check:

   Bind mounts = live code sync [OK]

Hint: Bind mounts sync host files live inside containers [OK]

Common Mistakes:

• Confusing bind mounts with Docker image creation
• Thinking bind mounts isolate container from host
• Assuming bind mounts update Docker software

2. Which of the following is the correct syntax to create a bind mount in Docker CLI?

easy

A. docker run --mount /host/path:/container/path image_name

B. docker run -mount bind:/host/path:/container/path image_name

C. docker run -bind /host/path:/container/path image_name

D. docker run -v /host/path:/container/path image_name

Solution

1. Step 1: Recall Docker bind mount syntax

   The correct way to specify a bind mount is using the -v or --volume flag with the format host_path:container_path.

2. Step 2: Check each option

   docker run -v /host/path:/container/path image_name uses -v /host/path:/container/path which is correct. Options A, C, and D use incorrect flags or syntax.

3. Final Answer:

   docker run -v /host/path:/container/path image_name -> Option D

4. Quick Check:

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

Hint: Use -v host_path:container_path for bind mounts [OK]

Common Mistakes:

• Using --mount without correct syntax
• Using non-existent flags like -bind
• Mixing mount types incorrectly

3. Given the command:
docker run -it -v /home/user/app:/app ubuntu bash
What will happen if you edit a file inside /home/user/app on the host while the container is running?

medium

A. The changes will appear immediately inside the container's /app directory

B. The container will crash due to file conflicts

C. The changes will not reflect inside the container until it is restarted

D. The container will create a copy of the file and ignore host changes

Solution

1. Step 1: Understand bind mount behavior

   The -v /home/user/app:/app option mounts the host folder directly into the container, so files are shared live.

2. Step 2: Effect of editing host files

   Editing files on the host folder /home/user/app will immediately reflect inside the container at /app because of the live bind mount.

3. Final Answer:

   The changes will appear immediately inside the container's /app directory -> Option A

4. Quick Check:

   Host edits = instant container updates [OK]

Hint: Host file edits show instantly inside container [OK]

Common Mistakes:

• Thinking container needs restart to see changes
• Assuming container crashes on file edits
• Believing container copies files instead of sharing

4. You run this command but changes on your host folder are NOT visible inside the container:
docker run -v app:/app ubuntu
What is the most likely problem?

medium

A. You used a named volume instead of a bind mount with an absolute host path

B. The container image ubuntu does not support volumes

C. You forgot to add the -it flags

D. The container is missing the /app directory

Solution

1. Step 1: Analyze the volume syntax

   The command uses -v app:/app which creates a named volume called 'app', not a bind mount from the host.

2. Step 2: Understand bind mount requirement

   Bind mounts require an absolute host path like /home/user/app. Using just 'app' creates a Docker-managed volume, so host folder changes won't reflect.

3. Final Answer:

   You used a named volume instead of a bind mount with an absolute host path -> Option A

4. Quick Check:

   Bind mounts need absolute host paths [OK]

Hint: Use absolute host path for bind mounts, not volume names [OK]

Common Mistakes:

• Confusing named volumes with bind mounts
• Forgetting absolute path on host
• Assuming all volumes sync host files

5. You want to develop a Node.js app inside Docker using bind mounts. Your host code is in /home/dev/myapp. Which command correctly sets up the container so that:
- The host code is live inside /usr/src/app in the container
- The container runs npm start
- You can edit code on host and see changes immediately

Choose the best command:

hard

A. docker run -v /home/dev/myapp:/usr/src/app node npm start

B. docker run -v /home/dev/myapp node npm start

C. docker run -v /home/dev/myapp:/usr/src/app -w /usr/src/app node npm start

D. docker run -v /usr/src/app:/home/dev/myapp node npm start

Solution

1. Step 1: Check bind mount and working directory

   docker run -v /home/dev/myapp:/usr/src/app -w /usr/src/app node npm start uses -v /home/dev/myapp:/usr/src/app to bind mount the host folder to the container path, and -w /usr/src/app to set the working directory inside the container.

2. Step 2: Confirm command and live editing

   Running npm start inside the container's working directory ensures the app runs with live code from the host. docker run -v /home/dev/myapp:/usr/src/app node npm start misses the working directory, docker run -v /home/dev/myapp node npm start has incorrect volume syntax (missing container path), and docker run -v /usr/src/app:/home/dev/myapp node npm start reverses paths incorrectly.

3. Final Answer:

   docker run -v /home/dev/myapp:/usr/src/app -w /usr/src/app node npm start -> Option C

4. Quick Check:

   Bind mount + correct workdir + command = docker run -v /home/dev/myapp:/usr/src/app -w /usr/src/app node npm start [OK]

Hint: Set -v host:container and -w container for live dev [OK]

Common Mistakes:

• Omitting working directory (-w) for commands
• Reversing host and container paths
• Not specifying full host path for bind mount