5.1.2.1 Dockerignore Dependency Folders

Excluding dependency folders through .dockerignore prevents locally installed packages — node_modules, Python virtual environments, vendored Go modules — from being unnecessarily included in the build context, since these are almost always reinstalled fresh inside the image rather than copied in from the host.

Why Dependency Folders Shouldn't Be in the Context

A Dockerfile typically installs dependencies itself, inside the image, using a manifest file as the source of truth — copying a locally installed dependency folder from the host is both unnecessary and potentially harmful, since it may include platform-specific binaries that don't match the image's environment.

node_modules
venv/
vendor/
__pycache__

A Concrete Example of the Problem

Without excluding node_modules, a locally installed dependency tree (often hundreds of megabytes) gets needlessly transferred as part of the build context, even though npm install inside the Dockerfile will reinstall everything fresh anyway.

COPY package*.json ./
RUN npm install
COPY . .

If node_modules is not excluded via .dockerignore, the final COPY . . could inadvertently overwrite the freshly installed dependencies with the host's locally installed (and potentially platform-mismatched) version.

Measuring the Impact of Excluding Dependency Folders

Comparing build context size with and without this exclusion in place typically reveals one of the most significant single reductions available from any individual .dockerignore pattern.

du -sh node_modules

This alone often represents a substantial fraction of an unoptimized build context's total size.

Why Excluding Dependency Folders Matters

Dependency folders are usually the single largest unnecessary contributor to build context size in most projects, and excluding them addresses both a performance concern (unnecessary transfer time) and a correctness concern (avoiding host-specific binaries silently overwriting a freshly installed, image-appropriate dependency tree).