Bind mounts for development in Docker - Step-by-Step Execution

Process Flow - Bind mounts for development

Start Docker Container

↓

Specify Bind Mount

↓

Host Folder Linked to Container

↓

Code Changes on Host

↓

Changes Reflected in Container

↓

Develop and Test Live

↓

Stop Container

This flow shows how a host folder is linked to a container using a bind mount, allowing live code changes on the host to appear instantly inside the container.

Execution Sample

Docker

docker run -it -v /host/app:/app myimage
# Start container with bind mount
# Edit files in /host/app on host
# Changes appear in /app inside container

This command runs a container with a bind mount linking the host's /host/app folder to the container's /app folder for live development.

Process Table

Step	Action	Host Folder State	Container Folder State	Result
1	Start container with bind mount	/host/app contains code v1	/app linked to /host/app	Container sees code v1
2	Edit file on host: change main.py	/host/app main.py updated to v2	/app main.py updated to v2	Container sees updated main.py
3	Run app inside container	No change	/app runs updated code v2	Live testing with latest code
4	Add new file on host: utils.py	/host/app utils.py added	/app utils.py appears	Container sees new file immediately
5	Stop container	Host folder unchanged	Container stops	Development session ends

💡 Container stops, bind mount ends but host files remain unchanged

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
/host/app/main.py	version 1	version 2	version 2	version 2
/host/app/utils.py	does not exist	does not exist	added	added
/app/main.py (container)	version 1	version 2	version 2	version 2
/app/utils.py (container)	does not exist	does not exist	added	added

Key Moments - 3 Insights

Why do changes on the host folder immediately appear inside the container?

Because the bind mount links the host folder directly to the container folder, so both share the same files in real time, as shown in execution_table steps 2 and 4.

Does stopping the container delete the files on the host?

No, stopping the container only ends the container process. The host files remain unchanged, as shown in execution_table step 5.

What happens if you add a new file on the host after the container started?

The new file appears immediately inside the container folder because the bind mount reflects all host folder changes live, as shown in execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of /app/main.py inside the container after step 2?

A File deleted

B Version 1 (original file)

C Version 2 (updated file)

D File does not exist

💡 Hint

Check the 'Container Folder State' column at step 2 in the execution_table.

At which step does the container first see the new file utils.py?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look for when utils.py appears in the 'Container Folder State' column in the execution_table.

If the bind mount was not used, what would happen to changes made on the host folder?

A They would appear live inside the container

B They would not appear inside the container

C The container would crash

D The host files would be deleted

💡 Hint

Recall that bind mounts link host and container folders live; without it, container files stay static.

Concept Snapshot

Bind mounts link a host folder to a container folder live.
Syntax: docker run -v /host/path:/container/path image
Changes on host appear instantly inside container.
Useful for live development and testing.
Stopping container does not affect host files.

Full Transcript

Bind mounts in Docker let you connect a folder on your computer (host) to a folder inside a running container. When you start a container with a bind mount, any changes you make to files on your computer show up immediately inside the container. This is great for development because you can edit code on your computer and test it live inside the container without rebuilding the image. The flow starts by running the container with the bind mount option. Then, when you edit or add files on your host, those changes appear inside the container folder. When you stop the container, the files on your computer stay safe and unchanged. This method helps developers work faster by seeing their changes live inside the container environment.