Build context concept in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Docker Build Context

What does the Docker build context include when you run docker build . in a directory?

A All files and folders in the current directory and its subdirectories are sent to the Docker daemon as the build context.

B Only the Dockerfile is sent to the Docker daemon as the build context.

C Only files explicitly listed in the Dockerfile are sent as the build context.

D Only files tracked by Git in the current directory are sent as the build context.

💡 Hint

Think about what files the Docker daemon needs access to during build.

The build context is the set of files located in the specified directory (and its subdirectories) that are sent to the Docker daemon. This allows the Dockerfile to reference these files during the build.

💻 Command Output

intermediate

Effect of Large Build Context on Docker Build

You run docker build . in a directory containing a 1GB video file not referenced in the Dockerfile. What is the most likely effect on the build process?

A The build will be slow because the entire 1GB file is sent as part of the build context to the Docker daemon.

B The build will be fast because Docker ignores files not referenced in the Dockerfile.

C The build will fail with an error about large files in the context.

D The build will only send the Dockerfile and ignore other files.

💡 Hint

Consider what files Docker sends to the daemon regardless of Dockerfile references.

Docker sends the entire directory content as the build context, even if some files are not used in the Dockerfile. Large files increase build time due to transfer overhead.

❓ Configuration

advanced

Optimizing Docker Build Context with .dockerignore

Which .dockerignore file content will exclude all .log files and the temp directory from the build context?

A

temp
*.log/

B

*.log
temp

C

temp/*
*.log

D

*.log
temp/

💡 Hint

Remember that directories should end with a slash to exclude them properly.

The .dockerignore file uses patterns similar to .gitignore. To exclude a directory, end its name with a slash. To exclude files by extension, use *.log.

❓ Troubleshoot

advanced

Why is my Docker build context unexpectedly large?

You notice your Docker build is very slow. You suspect the build context is too large. Which of the following is the most likely cause?

A You are using an outdated Docker version that slows down builds.

B Your Dockerfile has syntax errors causing slow builds.

C You forgot to add a <code>.dockerignore</code> file to exclude unnecessary files and folders.

D You are running <code>docker build</code> without specifying the Dockerfile.

💡 Hint

Think about what controls which files are sent to the Docker daemon.

If you don't exclude files with .dockerignore, all files in the directory are sent as build context, which can be very large and slow.

🔀 Workflow

expert

Correct Order of Steps to Optimize Docker Build Context

Arrange the steps in the correct order to optimize your Docker build context for faster builds.

A 1,2,3,4

B 3,1,2,4

C 1,3,2,4

D 3,2,1,4

💡 Hint

Think about preparing the Dockerfile before excluding files and building.

First, review the Dockerfile to reduce unnecessary file copies. Then create a .dockerignore to exclude files. Next, run the build. Finally, test and measure improvements.