Using .dockerignore - Commands & Configuration

Introduction

When building Docker images, unnecessary files can make the image bigger and slower to build. The .dockerignore file helps you tell Docker which files or folders to skip during the build, making the process faster and the image smaller.

When you want to exclude local files like logs or temporary files from your Docker image.

When your project has large folders like node_modules or build artifacts that are not needed inside the container.

When you want to speed up Docker builds by avoiding copying unnecessary files.

When you want to keep sensitive files like environment configs out of the Docker image.

When you want to reduce the size of the final Docker image for faster deployment.

Config File - .dockerignore

.dockerignore

node_modules
*.log
.git
.env
build/

This .dockerignore file tells Docker to ignore the node_modules folder, all files ending with .log, the .git folder, the .env file, and the build folder during the image build.

This keeps the image clean and small by excluding files that are not needed inside the container.

Commands

This command builds a Docker image named my-app-image using the current folder as the build context. Docker will use the .dockerignore file to skip unwanted files.

Terminal

docker build -t my-app-image .

Expected Output

[+] Building 5.3s (8/8) FINISHED

 => [internal] load build definition from Dockerfile 0.1s

 => [internal] load .dockerignore 0.0s

 => [internal] load metadata for docker.io/library/node:18 1.2s

 => [1/4] FROM docker.io/library/node:18@sha256:... 0.0s

 => [2/4] WORKDIR /app 0.0s

 => [3/4] COPY package.json package-lock.json ./ 0.5s

 => [4/4] RUN npm install 3.3s

 => exporting to image 0.1s

 => => exporting layers 0.1s

 => => writing image sha256:... 0.0s

Successfully built sha256:...

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    7a8b9c0d1e2f   10 seconds ago   350MB

Key Concept

If you remember nothing else from this pattern, remember: the .dockerignore file tells Docker which files to skip during build, making your images smaller and builds faster.

Common Mistakes

Not creating a .dockerignore file and copying all files including large or sensitive ones.

This makes the Docker image unnecessarily large and may expose sensitive data.

Create a .dockerignore file listing files and folders to exclude from the build context.

Using incorrect patterns in .dockerignore that do not match the files to exclude.

Docker will still copy unwanted files, defeating the purpose of .dockerignore.

Use correct syntax and test patterns to ensure the right files are ignored.

Summary

The .dockerignore file excludes files and folders from the Docker build context.

Use docker build with the current folder; Docker reads .dockerignore automatically.

Check the built image with docker images to confirm successful build.

Practice

1. What is the main purpose of a .dockerignore file in a Docker project?

easy

A. To specify environment variables for the Docker container

B. To tell Docker which files and folders to exclude when building an image

C. To configure network settings for Docker containers

D. To list all files that must be included in the Docker image

Solution

1. Step 1: Understand the role of .dockerignore

   The .dockerignore file lists files and folders Docker should skip during image build.

2. Step 2: Compare options with this role

   Only To tell Docker which files and folders to exclude when building an image correctly states that .dockerignore excludes files/folders from the build context.

3. Final Answer:

   To tell Docker which files and folders to exclude when building an image -> Option B

4. Quick Check:

   .dockerignore excludes files from build context [OK]

Hint: Think: .dockerignore tells Docker what NOT to include [OK]

Common Mistakes:

• Confusing .dockerignore with Dockerfile
• Thinking it lists files to include instead of exclude
• Assuming it configures container runtime settings

2. Which of the following is the correct syntax to ignore the node_modules folder in a .dockerignore file?

easy

A. node_modules

B. node_modules/*

C. /node_modules/*

D. !node_modules

Solution

1. Step 1: Review .dockerignore syntax for ignoring folders

   Simply writing the folder name like node_modules ignores it and all its contents.

2. Step 2: Analyze options

   A (node_modules) is correct because it ignores the folder and its contents. B (node_modules/*) and C (/node_modules/*) ignore only contents, leaving an empty folder in the build context. D (!node_modules) negates ignoring, so it includes the folder.

3. Final Answer:

   node_modules -> Option A

4. Quick Check:

   Folder name alone ignores folder and contents [OK]

Hint: Write folder name alone to ignore it fully [OK]

Common Mistakes:

• Using ! to ignore instead of include
• Adding slashes inconsistently
• Confusing .dockerignore with .gitignore syntax

3. Given this .dockerignore content:

node_modules
secret.txt
!secret.txt.bak

Which files will be included in the Docker build context?

medium

A. secret.txt and secret.txt.bak only

B. node_modules folder, secret.txt, secret.txt.bak

C. node_modules folder and secret.txt.bak only

D. secret.txt.bak only

Solution

1. Step 1: Interpret the .dockerignore rules

   Lines exclude node_modules and secret.txt. The !secret.txt.bak line re-includes secret.txt.bak.

2. Step 2: Determine included files

   Excluded: node_modules and secret.txt. Included: secret.txt.bak because of the ! rule.

3. Final Answer:

   secret.txt.bak only -> Option D

4. Quick Check:

   ! negates ignore = include secret.txt.bak [OK]

Hint: ! before filename re-includes it despite ignore [OK]

Common Mistakes:

• Assuming ! negates all ignores
• Including ignored folders by mistake
• Ignoring the order of rules

4. You wrote this .dockerignore file:

node_modules
!node_modules/package.json

But package.json is still excluded from the build. What is the likely problem?

medium

A. Docker does not support negation (!) in .dockerignore

B. You must restart Docker daemon to apply .dockerignore changes

C. Negation does not work on files inside ignored folders

D. The syntax for negation is incorrect; use double exclamation marks (!!)

Solution

1. Step 1: Understand negation behavior in .dockerignore

   Negation (!) cannot re-include files inside a folder that is ignored entirely.

2. Step 2: Analyze the problem

   Since node_modules is ignored, negating node_modules/package.json does not include it back.

3. Final Answer:

   Negation does not work on files inside ignored folders -> Option C

4. Quick Check:

   Negation inside ignored folder fails [OK]

Hint: Negation can't rescue files inside ignored folders [OK]

Common Mistakes:

• Thinking negation always works
• Restarting Docker unnecessarily
• Using wrong negation syntax

5. You want to speed up your Docker build by excluding all .log files except important.log in the root folder. Which .dockerignore content achieves this?

hard

A. *.log
!important.log

B. *.log
!important.log
!important.log

C. *.log
!important.log
!important/*.log

D. *.log
!important.log
!important/

Solution

1. Step 1: Write rule to ignore all .log files

   Using *.log ignores all files ending with .log anywhere.

2. Step 2: Use negation to include only important.log in root

   !important.log re-includes that specific file in the root folder.

3. Final Answer:

   *.log\n!important.log -> Option A

4. Quick Check:

   Ignore all .log, then include important.log [OK]

Hint: Ignore *.log then negate important.log to include it [OK]

Common Mistakes:

• Repeating negation lines unnecessarily
• Negating folders instead of files
• Using wrong paths for negation