Using .dockerignore - Step-by-Step Execution

Process Flow - Using .dockerignore

Start Docker Build

↓

Read .dockerignore file

↓

Check each file/folder in context

↓

If matches .dockerignore pattern?

Yes→Exclude from build context

No↓

Include in build context

↓

Send build context to Docker daemon

↓

Build image with included files

↓

Finish

Docker reads the .dockerignore file to exclude specified files/folders from the build context before building the image.

Execution Sample

Docker

FROM alpine
COPY . /app
RUN ls /app

Builds an image copying current folder except files ignored by .dockerignore, then lists copied files.

Process Table

Step	File/Folder Checked	Matches .dockerignore?	Action	Build Context State
1	node_modules/	Yes	Exclude	All files except node_modules/
2	README.md	No	Include	README.md included
3	src/	No	Include	src/ included
4	.git/	Yes	Exclude	node_modules/, .git/ excluded
5	Dockerfile	No	Include	Dockerfile included
6	temp.log	Yes	Exclude	node_modules/, .git/, temp.log excluded
7	All files checked	-	-	Final context excludes node_modules/, .git/, temp.log

💡 All files checked; excluded files are not sent to Docker daemon for build.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	Final
Build Context	All files	Exclude node_modules/	Include README.md	Include src/	Exclude .git/	Include Dockerfile	Exclude temp.log	Final context excludes node_modules/, .git/, temp.log

Key Moments - 2 Insights

Why are some files not copied into the Docker image even though they exist in the folder?

Because those files match patterns in .dockerignore and are excluded from the build context, as shown in execution_table steps 1, 4, and 6.

Does .dockerignore affect files copied by COPY commands inside the Dockerfile?

Yes, because COPY only copies files present in the build context. Files excluded by .dockerignore are not in the context and thus not copied, as seen in the final build context state.

Visual Quiz - 3 Questions

Look at the execution table, which file/folder is excluded at step 4?

A README.md

B src/

C .git/

D Dockerfile

💡 Hint

Check the 'File/Folder Checked' and 'Matches .dockerignore?' columns at step 4.

At which step is 'temp.log' excluded from the build context?

A Step 6

B Step 3

C Step 2

D Step 5

💡 Hint

Look for 'temp.log' in the 'File/Folder Checked' column and see the action taken.

If you remove 'node_modules/' from .dockerignore, what changes in the build context?

A node_modules/ will still be excluded

B node_modules/ will be included in the build context

C All files will be excluded

D Only Dockerfile will be included

💡 Hint

Refer to the variable_tracker showing exclusion of node_modules/ and understand .dockerignore effect.

Concept Snapshot

Using .dockerignore:
- Place .dockerignore in build context root
- List files/folders to exclude from build context
- Docker skips these during build context upload
- Speeds up build and reduces image size
- Patterns support wildcards and negation

Full Transcript

When Docker builds an image, it sends all files in the build folder to the Docker daemon. The .dockerignore file tells Docker which files or folders to skip. This helps avoid sending unnecessary files like node_modules or .git. Docker reads .dockerignore first, then checks each file. If a file matches a pattern, it is excluded from the build context. Only included files are sent and can be copied into the image. This makes builds faster and images smaller. For example, if node_modules/ is in .dockerignore, it won't be copied into the image even if the Dockerfile says COPY . /app. The execution table shows each file checked and whether it is included or excluded. The variable tracker shows how the build context changes step by step. Understanding this helps avoid accidentally copying large or sensitive files into images.

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