Build context concept in Docker - Commands & Configuration

Introduction

When you build a Docker image, Docker needs to know which files to include. The build context is the folder and its contents that Docker uses to find files during the build. It helps Docker copy files into the image and run commands on them.

When you want to include your app files inside a Docker image

When you need to copy configuration files into the image during build

When you want to run commands on files that are part of your project during image creation

When you want to avoid sending unnecessary files to Docker to speed up the build

When you want to organize your Dockerfile and related files in one folder

Commands

This command builds a Docker image named 'my-app-image' using the folder './app' as the build context. Docker will look inside './app' for the Dockerfile and any files needed during the build.

Terminal

docker build -t my-app-image ./app

Expected Output

Sending build context to Docker daemon  4.096kB

Step 1/3 : FROM alpine:3.18

3.18: Pulling from library/alpine

Digest: sha256:...

Status: Downloaded newer image for alpine:3.18

 ---> 3f53bb00af94

Step 2/3 : COPY . /app

 ---> Using cache

 ---> 7a8b9c1d2e3f

Step 3/3 : CMD ["/app/start.sh"]

 ---> Running in 9c8d7e6f5a4b

Removing intermediate container 9c8d7e6f5a4b

 ---> 1a2b3c4d5e6f

Successfully built 1a2b3c4d5e6f

Successfully tagged my-app-image:latest

→

-t - Assigns a name and optionally a tag to the image

This command lists the Docker images named 'my-app-image' to verify the image was built successfully.

Terminal

docker images my-app-image

Expected Output

REPOSITORY      TAG       IMAGE ID       CREATED          SIZE

my-app-image    latest    1a2b3c4d5e6f   10 seconds ago   5.6MB

Key Concept

The build context is the folder Docker uses to find files during image build; only files inside this folder can be accessed in the Dockerfile.

Common Mistakes

Running 'docker build' with the wrong folder as context

Docker cannot find the Dockerfile or needed files, causing build errors.

Always specify the folder containing your Dockerfile and related files as the build context.

Including large unnecessary files in the build context

This slows down the build because Docker sends all context files to the daemon.

Use a .dockerignore file to exclude files and folders not needed for the build.

Summary

The build context is the folder Docker uses to find files during image build.

Use 'docker build -t image-name path' where 'path' is the build context folder.

Keep the build context small to speed up builds and avoid errors.

Practice

1. What does the build context specify when running docker build?

easy

A. The name of the Docker image to create

B. The folder Docker uses to find files for building the image

C. The network settings for the container

D. The port mapping for the container

Solution

1. Step 1: Understand the role of build context

   The build context is the directory Docker looks into to find files needed for the image build.

2. Step 2: Identify the correct description

   Among the options, only the folder used to find files matches the build context definition.

3. Final Answer:

   The folder Docker uses to find files for building the image -> Option B

4. Quick Check:

   Build context = folder path [OK]

Hint: Build context is the folder path at the end of docker build [OK]

Common Mistakes:

• Confusing build context with image name
• Thinking build context is network or port settings
• Assuming build context is a Dockerfile option

2. Which of the following is the correct syntax to specify the build context when building a Docker image?

easy

A. docker build -context /path/to/context -t myimage

B. docker build /path/to/context -t myimage

C. docker build -t myimage /path/to/context

D. docker build -buildcontext /path/to/context -t myimage

Solution

1. Step 1: Recall docker build command syntax

   The build context path is given as the last argument in the command, after options like -t.

2. Step 2: Check each option

   docker build -t myimage /path/to/context places the context path last, which is correct. Options C and D use invalid flags. docker build /path/to/context -t myimage places context before -t, which is incorrect syntax.

3. Final Answer:

   docker build -t myimage /path/to/context -> Option C

4. Quick Check:

   Context path is last argument in docker build [OK]

Hint: Build context path is always last in docker build command [OK]

Common Mistakes:

• Using invalid flags like -context or -buildcontext
• Placing context path before options
• Omitting the context path entirely

3. Given this command:
docker build -t appimage .
and a .dockerignore file that excludes node_modules/, what will happen to the node_modules folder during build?

medium

A. It will be sent to the Docker daemon as part of the build context

B. It will be copied into the image automatically

C. It will cause an error during build

D. It will be excluded from the build context and not sent

Solution

1. Step 1: Understand .dockerignore effect

   The .dockerignore file tells Docker which files or folders to exclude from the build context sent to the daemon.

2. Step 2: Apply to node_modules folder

   Since node_modules/ is listed in .dockerignore, it will be excluded and not sent during build.

3. Final Answer:

   It will be excluded from the build context and not sent -> Option D

4. Quick Check:

   .dockerignore excludes files from build context [OK]

Hint: Files in .dockerignore are NOT sent in build context [OK]

Common Mistakes:

• Thinking excluded files cause build errors
• Assuming excluded files are still copied into image
• Confusing build context with container runtime files

4. You run docker build -t myapp without specifying a build context. What will happen?

medium

A. Docker will throw an error about missing build context

B. Docker will use the current directory as the build context

C. Docker will build an empty image

D. Docker will use the root directory as build context

Solution

1. Step 1: Check docker build command requirements

   The docker build command requires a build context path as the last argument.

2. Step 2: Analyze missing context behavior

   If no context is given, Docker will report an error about missing build context.

3. Final Answer:

   Docker will throw an error about missing build context -> Option A

4. Quick Check:

   Build context is mandatory argument [OK]

Hint: Always specify build context path in docker build [OK]

Common Mistakes:

• Assuming current directory is default context
• Expecting build to succeed without context
• Confusing build context with Dockerfile location

5. You want to build a Docker image but exclude large log files and temporary folders from the build context to speed up the build. Which approach is best?

hard

A. Use a .dockerignore file listing logs and temp folders

B. Manually delete logs and temp folders before building

C. Specify the build context as the parent directory

D. Use the --exclude flag in docker build

Solution

1. Step 1: Identify how to exclude files from build context

   The .dockerignore file is designed to exclude files and folders from the build context sent to Docker.

2. Step 2: Evaluate other options

   Manually deleting files is error-prone. Specifying parent directory increases context size. There is no --exclude flag in docker build.

3. Final Answer:

   Use a .dockerignore file listing logs and temp folders -> Option A

4. Quick Check:

   .dockerignore controls build context contents [OK]

Hint: Use .dockerignore to exclude unwanted files from build context [OK]

Common Mistakes:

• Trying to exclude files with non-existent flags
• Forgetting to create .dockerignore file
• Using wrong directory as build context