Q: A developer has a project with a 10GB `data/` directory containing training datasets. Every `docker build` takes 15 minutes before even executing the first Dockerfile instruction. The Dockerfile doesn't reference the `data/` directory at all. Why is it so slow?
Before executing any Dockerfile instruction, Docker packages the entire build context (the directory passed to docker build) and transfers it to the Docker daemon.
.dockerignore.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Want to master this scenario in a live sandbox? KodeKloud's Docker Certified Associate (DCA) Hands-On Lab Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When containerizing our microservices stack, container lifecycle and resource management were critical. The interviewer is testing: Docker build context transfer, .dockerignore.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Before executing any Dockerfile instruction, Docker packages the entire build context (the directory passed to docker build) and transfers it to the Docker daemon. If the data/ directory is inside the build context, Docker transfers all 10GB every single build — even though no COPY or ADD references it. The "Sending build context to Docker daemon... 10GB" message in the build output confirms this. *Fix:* Add data/ to .dockerignore: This reduces the build context to only the files the Dockerfile actually needs. Alternatively, restructure the project so the Dockerfile lives in a subdirectory without the data, or use BuildKit's ability to specify individual files via --build-context.
data/
*.csv
*.parquet
__pycache__/
.git/
- Immediate Triage: Before executing any Dockerfile instruction, Docker packages the entire build context (the dire
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Structuring Dockerfile instructions inefficiently by copying app source before package manifests when configuring developer project 10GB
Copying code before package manifests (
package.json,go.mod,requirements.txt) invalidates the build cache on every commit, forcing slow full reinstalls. -
Neglecting the PID 1 process reap problem and omitting proper SIGTERM signal forwarding when configuring developer project 10GB
If an application runs as PID 1 without an init system (like
tini), it fails to reap zombie child processes and ignoresSIGTERMsignals, causing unclean 10s timeouts. - Assembling single-stage images containing compilers, build SDKs, and header files in production when configuring developer project 10GB Single-stage builds bloat image size by gigabytes and expose extensive package vulnerabilities; multi-stage builds isolate artifacts into minimal distroless images.
- Confusing container port forwarding on bridge networks with unisolated host networking mode when configuring developer project 10GB Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.