Cache mount for faster builds in Docker - Mini Project: Build & Apply

Cache mount for faster builds

📖 Scenario: You are working on a Docker project where you want to speed up the build process by using cache mounts. This helps reuse downloaded packages and dependencies instead of fetching them every time.

🎯 Goal: Build a Dockerfile that uses --mount=type=cache to cache package manager files and speed up the build.

📋 What You'll Learn

Create a Dockerfile with a base image python:3.12-slim

Add a cache mount for the /root/.cache/pip directory during package installation

Install the requests package using pip with the cache mount

Print a message to confirm the build step

💡 Why This Matters

🌍 Real World

Caching speeds up Docker builds by reusing downloaded files, saving time and bandwidth.

💼 Career

DevOps engineers use cache mounts to optimize CI/CD pipelines and reduce build times.

1

Create the base Dockerfile

Create a Dockerfile starting with the base image python:3.12-slim using the FROM instruction.

Docker

# Your code here

Hint

Use the FROM keyword followed by the exact image name python:3.12-slim.

2

Add a cache mount for pip cache

Add a RUN instruction that uses --mount=type=cache,target=/root/.cache/pip to cache pip files during package installation.

Docker

FROM python:3.12-slim
# Your code here

Hint

Use RUN --mount=type=cache,target=/root/.cache/pip pip install requests exactly.

3

Add a confirmation message

Modify the RUN instruction to print "Installed requests with cache" after installing the package.

Docker

FROM python:3.12-slim
RUN --mount=type=cache,target=/root/.cache/pip pip install requests
# Your code here

Hint

Use sh -c to run both commands in one RUN instruction.

4

Build and verify the Docker image

Build the Docker image and run it to verify the output contains Installed requests with cache.

Docker

FROM python:3.12-slim
RUN --mount=type=cache,target=/root/.cache/pip sh -c "pip install requests && echo 'Installed requests with cache'"
# Your code here

Hint

Run docker build --progress=plain . and check the output for the confirmation message.

Practice

1. What is the main purpose of using --mount=type=cache in a Dockerfile during build?

easy

A. To save files between build steps and speed up future builds

B. To permanently store files in the final image

C. To share files between running containers

D. To mount host directories into the container at runtime

Solution

1. Step 1: Understand cache mount purpose

   The --mount=type=cache option is used during build to save files temporarily between build steps.

2. Step 2: Identify effect on build speed

   By saving files like package downloads, it avoids repeating work, making future builds faster.

3. Final Answer:

   To save files between build steps and speed up future builds -> Option A

4. Quick Check:

   Cache mount speeds builds = D [OK]

Hint: Cache mounts save build files to speed up next builds [OK]

Common Mistakes:

• Confusing cache mount with runtime volume mount
• Thinking cache mount stores files in final image
• Assuming cache mount shares files between containers

2. Which of the following is the correct syntax to use a cache mount in a Dockerfile RUN command?

easy

A. RUN --mount=type=volume,target=/root/.cache npm install

B. RUN --cache=type=mount,target=/root/.cache npm install

C. RUN --mount=cache,target=/root/.cache npm install

D. RUN --mount=type=cache,target=/root/.cache npm install

Solution

1. Step 1: Check correct mount syntax

   The correct syntax uses --mount=type=cache,target=... inside the RUN command.

2. Step 2: Validate options

   RUN --mount=type=cache,target=/root/.cache npm install matches the correct syntax exactly; others have wrong keywords or types.

3. Final Answer:

   RUN --mount=type=cache,target=/root/.cache npm install -> Option D

4. Quick Check:

   Correct cache mount syntax = A [OK]

Hint: Use --mount=type=cache,target=... exactly in RUN [OK]

Common Mistakes:

• Using --cache instead of --mount
• Omitting type=cache
• Using type=volume instead of cache

3. Given this Dockerfile snippet:

RUN --mount=type=cache,target=/root/.cache pip install -r requirements.txt
RUN --mount=type=cache,target=/root/.cache pip install -r requirements.txt

What is the expected effect on build time when running the second RUN command?

medium

A. The second RUN command will be slower because cache is cleared

B. The second RUN command will be faster because it reuses cached files

C. The second RUN command will fail due to cache mount conflict

D. The second RUN command ignores cache and runs normally

Solution

1. Step 1: Understand cache mount effect on repeated commands

   The cache mount stores files from the first pip install in /root/.cache.

2. Step 2: Predict second RUN command behavior

   The second RUN reuses cached files, so it runs faster by skipping downloads.

3. Final Answer:

   The second RUN command will be faster because it reuses cached files -> Option B

4. Quick Check:

   Cache reuse speeds second build step = B [OK]

Hint: Cache mount speeds repeated installs by reusing files [OK]

Common Mistakes:

• Assuming cache clears between RUN commands
• Thinking cache causes build failure
• Believing cache is ignored during build

4. You wrote this Dockerfile line:

RUN --mount=type=cache,target=/root/.cache npm install

But the cache is not speeding up builds. What is the likely mistake?

medium

A. The cache mount target directory is incorrect or not used by npm

B. You forgot to add --cache flag instead of --mount

C. Cache mounts only work with Python, not npm

D. You must run docker build with --no-cache option

Solution

1. Step 1: Check cache mount target relevance

   Cache mount must target the directory where npm stores cache files, usually /root/.npm, not /root/.cache.

2. Step 2: Understand npm cache usage

   If the target directory is wrong, npm won't use the cache, so builds stay slow.

3. Final Answer:

   The cache mount target directory is incorrect or not used by npm -> Option A

4. Quick Check:

   Correct cache target directory needed = C [OK]

Hint: Match cache target to tool's actual cache folder [OK]

Common Mistakes:

• Using wrong directory for cache mount target
• Confusing --cache and --mount flags
• Thinking cache mounts only work for some languages

5. You want to speed up a Docker build that uses apt-get update and apt-get install. How can you use cache mounts to optimize this build?

hard

A. Use RUN --mount=type=cache,target=/etc/apt before apt-get update

B. Use RUN --mount=type=cache,target=/var/lib/apt after apt-get install

C. Use RUN --mount=type=cache,target=/var/cache/apt before apt-get update

D. Use RUN --mount=type=cache,target=/usr/bin/apt before apt-get update

Solution

1. Step 1: Identify apt cache directory

   The apt package manager stores downloaded package files in /var/cache/apt.

2. Step 2: Apply cache mount before update

   Mounting cache at /var/cache/apt before apt-get update saves downloaded package lists and speeds up future runs.

3. Final Answer:

   Use RUN --mount=type=cache,target=/var/cache/apt before apt-get update -> Option C

4. Quick Check:

   Cache apt downloads at /var/cache/apt = A [OK]

Hint: Cache package manager download folders to speed builds [OK]

Common Mistakes:

• Mounting wrong directories like /etc/apt or /usr/bin/apt
• Mounting cache after install instead of before update
• Confusing apt cache with config directories