Hot reloading with bind mounts in Docker - Mini Project: Build & Apply

Hot Reloading with Bind Mounts in Docker

📖 Scenario: You are developing a simple web application using Docker. You want to see your code changes immediately without rebuilding the Docker image every time. This is called hot reloading.To achieve this, you will use a bind mount to link your local code folder to the container's code folder.

🎯 Goal: Build a Docker setup that uses a bind mount to enable hot reloading of your application code inside the container.

📋 What You'll Learn

Create a Dockerfile with a basic web server setup

Create a docker-compose.yml file with a bind mount from local code to container

Run the container so that code changes on the host reflect immediately inside the container

Print the container logs to verify hot reloading

💡 Why This Matters

🌍 Real World

Developers often want to see their code changes immediately without rebuilding containers. Bind mounts let the container use local code files directly, enabling fast development cycles.

💼 Career

Understanding hot reloading with Docker bind mounts is essential for DevOps roles to improve developer productivity and streamline containerized application development.

1

Create a simple Dockerfile for a Python web server

Create a file named Dockerfile with these exact lines to set up a Python 3.12 environment and copy the app.py file into the container's /app folder:

Docker

# Your code here

Hint

Use the official Python 3.12 slim image. Set working directory to /app. Copy app.py from your local folder to the container. Set the command to run python app.py.

2

Create a docker-compose.yml with a bind mount for hot reloading

Create a file named docker-compose.yml with a service called web that uses the current directory as a bind mount to /app inside the container. Use the Dockerfile you created and expose port 8000:8000.

Docker

FROM python:3.12-slim
RUN pip install flask
WORKDIR /app
COPY app.py /app/app.py
CMD ["python", "app.py"]

# Your code here

Hint

Use volumes to bind mount the current folder . to /app inside the container. This lets the container see your local code changes immediately.

3

Create a simple Python web app that reloads on code change

Create a file named app.py with a simple Flask web server that runs on port 8000 and prints Hello, World!. Use the debug=True option to enable hot reloading.

Docker

FROM python:3.12-slim
RUN pip install flask
WORKDIR /app
COPY app.py /app/app.py
CMD ["python", "app.py"]

version: '3.8'
services:
  web:
    build: .
    ports:
      - "8000:8000"
    volumes:
      - .:/app

# Your code here

Hint

Use Flask to create a web server. The debug=True option enables hot reloading inside the container.

4

Run the container and verify hot reloading

Run docker-compose up in your terminal to start the container. Then, open http://localhost:8000 in your browser. Change the text in app.py from Hello, World! to Hello, Docker! and save. Refresh the browser to see the updated text. Finally, print "Hot reloading works!" in your Python code and run it.

Docker

FROM python:3.12-slim
RUN pip install flask
WORKDIR /app
COPY app.py /app/app.py
CMD ["python", "app.py"]

version: '3.8'
services:
  web:
    build: .
    ports:
      - "8000:8000"
    volumes:
      - .:/app

from flask import Flask
app = Flask(__name__)

@app.route('/')
def hello():
    return "Hello, World!"

if __name__ == '__main__':
    app.run(host='0.0.0.0', port=8000, debug=True)

# Add a print statement below to confirm hot reloading
# Your code here

Hint

Use print("Hot reloading works!") inside the if __name__ == '__main__': block to confirm the app runs and reloads.

Practice

1. What is the main purpose of using bind mounts in Docker for hot reloading?

easy

A. To isolate container files from the host

B. To create a backup of container files

C. To increase container startup speed

D. To link local files to the container for instant updates

Solution

1. Step 1: Understand bind mounts role

   Bind mounts connect files from your computer directly into the container.

2. Step 2: Recognize hot reloading benefit

   This connection allows changes on your computer to appear immediately inside the container.

3. Final Answer:

   To link local files to the container for instant updates -> Option D

4. Quick Check:

   Bind mounts = instant file updates [OK]

Hint: Bind mounts sync local files live to container [OK]

Common Mistakes:

• Thinking bind mounts create backups
• Believing bind mounts speed up container start
• Assuming bind mounts isolate files

2. Which of the following is the correct syntax to run a Docker container with a bind mount for hot reloading?

easy

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

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

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

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

Solution

1. Step 1: Recall Docker bind mount syntax

   The correct flag for bind mounts is '-v' followed by host and container paths separated by a colon.

2. Step 2: Check options for correctness

   Only docker run -v /host/path:/container/path image_name uses '-v' with correct path format; others use invalid flags.

3. Final Answer:

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

4. Quick Check:

   Bind mount flag = -v [OK]

Hint: Use -v for bind mounts in docker run [OK]

Common Mistakes:

• Using --mount without proper syntax
• Using -bind or -link which are invalid
• Mixing up host and container paths

3. Given this command: docker run -v $(pwd)/app:/usr/src/app mynodeapp, what happens when you edit a file inside the local app folder?

medium

A. The container crashes due to file conflicts

B. The container ignores changes until restarted

C. The container's /usr/src/app files update immediately without restart

D. The container copies files back to the host folder

Solution

1. Step 1: Understand bind mount effect

   The command mounts the local 'app' folder into the container path '/usr/src/app'.

2. Step 2: Recognize hot reloading behavior

   Editing files locally updates the container files instantly because of the bind mount.

3. Final Answer:

   The container's /usr/src/app files update immediately without restart -> Option C

4. Quick Check:

   Bind mount = instant container file update [OK]

Hint: Local edits reflect instantly inside container [OK]

Common Mistakes:

• Thinking container needs restart to see changes
• Assuming container crashes on file change
• Believing files copy back to host automatically

4. You set up a bind mount with docker run -v /home/user/app:/app myapp but changes in /home/user/app do not reflect inside the container. What is the likely cause?

medium

A. The container overwrites /app on start, hiding host changes

B. The -v flag syntax is incorrect

C. Docker daemon is not running

D. The host path /home/user/app does not exist

Solution

1. Step 1: Check bind mount behavior on container start

   If the container image has files in /app, they may overwrite the mount, hiding host changes.

2. Step 2: Verify other options

   The syntax is correct, Docker daemon running is assumed, and path existence usually causes errors, not silent failure.

3. Final Answer:

   The container overwrites /app on start, hiding host changes -> Option A

4. Quick Check:

   Container files can hide bind mount changes [OK]

Hint: Check if container files overwrite mount path [OK]

Common Mistakes:

• Assuming syntax error without checking
• Ignoring container image files at mount path
• Not verifying host path existence

5. You want to enable hot reloading for a Node.js app inside Docker using bind mounts. Which approach best ensures code changes reflect immediately without restarting the container?

hard

A. Copy files into container at build time and run node app.js

B. Use docker run -v $(pwd):/app and run nodemon inside the container

C. Use docker run -v $(pwd):/app and run node app.js inside the container

D. Run container without volumes and restart container on changes

Solution

1. Step 1: Understand hot reloading needs

   Hot reloading requires file changes to be seen by the running app without restart.

2. Step 2: Choose correct tools and setup

   Bind mount syncs files, and using 'nodemon' watches for changes and reloads automatically.

3. Final Answer:

   Use docker run -v $(pwd):/app and run nodemon inside the container -> Option B

4. Quick Check:

   Bind mount + nodemon = hot reload [OK]

Hint: Combine bind mount with nodemon for live reload [OK]

Common Mistakes:

• Running node without watcher misses changes
• Copying files at build loses live update
• Restarting container manually wastes time