What is a .dockerignore File?

A .dockerignore file tells Docker which files and directories to exclude from the build context. Similar to .gitignore for Git, it reduces the amount of files sent to the Docker daemon, making builds faster and more efficient.

When you run docker build, Docker creates a build context by packaging all files in the build directory. By excluding unnecessary files like node_modules, .git, logs, and IDE settings, you significantly reduce build times and keep your Docker images lean.

This is especially important in CI/CD pipelines where every second counts. A well-configured .dockerignore can reduce build context size by 50-90%, depending on your project structure.

How to Use .dockerignore

Implementation Steps

Follow these steps to use .dockerignore:

Step 1: Create .dockerignore in your project root (same directory as Dockerfile)

Step 2: Add patterns for files/directories to exclude (one per line)

Step 3: Use wildcards: * (matches anything) and ? (single char)

Step 4: Add comments with # prefix for documentation

Step 5: Run docker build - patterns are automatically applied

Real-World Example

Node.js project .dockerignore:

File:

# Dependencies
node_modules/
npm-debug.log*

# Build outputs
dist/
build/

# Environment files
.env
.env.local

# Version control
.git
.gitignore

# IDE settings
.vscode/
.idea/

# OS files
.DS_Store
Thumbs.db

Impact:

• Faster builds - excludes 200MB+ node_modules

• Enhanced security - no .env files with secrets

• Cleaner images - no build artifacts or IDE files

• Better caching - improved Docker layer efficiency

Frequently Asked Questions

Does .dockerignore affect my final application?

No. Files in .dockerignore are excluded from the build context but not from the final image if they already exist. It only prevents copying unnecessary files during the build process.

What's the difference between .dockerignore and .gitignore?

.gitignore controls which files Git tracks; .dockerignore controls which files are sent to Docker during build. You can have different ignore patterns for each.

Should I exclude node_modules?

Yes! Your Dockerfile should run 'npm install' during build. Excluding node_modules keeps your build context small and ensures dependencies are fresh.

How accurate is the pattern test matcher?

The test matcher is approximate and simplified. It matches basic glob patterns (* and ?) but does not handle all Docker's .dockerignore semantics (directory rules, anchored paths, negations with !). Always test your generated file with 'docker build' to verify behavior.

Can I exclude and then include specific files?

Yes. Use ! prefix to negate a pattern. Example: exclude * then include with !important-file.txt (order matters).

How much can .dockerignore reduce build time?

Typically 20-80% reduction, depending on your project. Projects with large node_modules or .git directories see the most improvement.

Does .dockerignore work with docker compose?

Yes. Docker Compose uses the same .dockerignore file when building images specified in the compose.yml file.

Dockerignore Generator