⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Docker & Containers Interview Questions Scenario 84 of 159 in Docker & Containers
Staff SRE / Principal Architect [L3] Docker Must enable BuildKit Staff SRE Scenario [L3]
🎯 Target Role / Context: Docker Scenario #85 (L3) · Must enable BuildKit

Q: After months of daily Docker builds, your production server's disk is full. You run `docker system prune -af` and reclaim some space, but the disk is still 90% full. `docker system df` shows minimal usage. Where is the hidden disk consumption?

docker system prune only removes objects tracked by the Docker daemon (images, containers, volumes, build cache).

#Docker #Must enable BuildKit #L3 #Containers #Linux
🎙️ Candidate Opening & Architectural Context
""When containerizing our microservices stack, container lifecycle and resource management were critical. The interviewer is testing: overlay2 layer directory orphans, /var/lib/docker internals.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

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: overlay2 layer directory orphans, /var/lib/docker internals.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Production Solution & Architecture

docker system prune only removes objects tracked by the Docker daemon (images, containers, volumes, build cache). If the Docker daemon crashed or was force-killed during container operations, orphaned layer directories can accumulate in /var/lib/docker/overlay2/ that the daemon no longer tracks. *Diagnosis:* Run du -sh /var/lib/docker/overlay2/ and compare with docker system df. A large discrepancy confirms orphaned layers. *Fix:* The safest approach is to stop the Docker daemon (systemctl stop docker), back up any critical volumes, and reset the storage entirely (rm -rf /var/lib/docker). Restarting Docker recreates the directory structure. Re-pull needed images. For prevention, ensure the Docker daemon shuts down gracefully and monitor /var/lib/docker disk usage independently.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: docker system prune only removes objects tracked by the Docker daemon (images, containers, volumes, build cache). If the Docker da."
⚡ 60-Second Elevator Pitch Talking Points
  • Immediate Triage: docker system prune only removes objects tracked by the Docker daemon (images, containers, volu
  • Run targeted verification commands before modifying configuration.
  • Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Structuring Dockerfile instructions inefficiently by copying app source before package manifests when configuring months daily Docker Copying code before package manifests (package.json, go.mod, requirements.txt) invalidates the build cache on every commit, forcing slow full reinstalls.
  2. Neglecting the PID 1 process reap problem and omitting proper SIGTERM signal forwarding when configuring months daily Docker If an application runs as PID 1 without an init system (like tini), it fails to reap zombie child processes and ignores SIGTERM signals, causing unclean 10s timeouts.
  3. Assembling single-stage images containing compilers, build SDKs, and header files in production when configuring months daily Docker Single-stage builds bloat image size by gigabytes and expose extensive package vulnerabilities; multi-stage builds isolate artifacts into minimal distroless images.
  4. Confusing container port forwarding on bridge networks with unisolated host networking mode when configuring months daily Docker Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.
Advertisement
Want more Docker & Containers scenarios?
Explore our complete collection of scenario-based Docker & Containers interview runbooks.
Browse All Docker & Containers Questions →