⚡ ~/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 93 of 159 in Docker & Containers
Senior DevOps / SRE [L2] Docker Must enable BuildKit Production Scenario [L2]
🎯 Target Role / Context: Docker Scenario #94 (L2) · Must enable BuildKit

Q: Your Docker Compose file defines 15 services, but during local development, you only need 4 of them running. Starting all 15 wastes resources and slows down your machine. How do you selectively start subsets of services without maintaining multiple Compose files?

Use Compose Profiles (introduced in Docker Compose v1.28):

#Docker #Must enable BuildKit #L2 #Containers #Linux #Grafana
🎙️ Candidate Opening & Architectural Context
""In an interview, I explain how we diagnosed container runtime failures without guessing. The interviewer is testing: Docker Compose profiles.. 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: "In an interview, I explain how we diagnosed container runtime failures without guessing. The interviewer is testing: Docker Compose profiles.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Use Compose Profiles (introduced in Docker Compose v1.28):

  • docker compose up — starts only services without profiles (api).
  • docker compose --profile backend up — starts api + worker.
  • docker compose --profile full up — starts everything.
2️⃣

Remediation & Permanent Safeguards

Services without a profiles key always start. Services with profiles only start when that profile is explicitly activated: This is cleaner than docker compose up service1 service2 because profiles logically group related services and can be combined.

services:
  api:
    image: myapi
    # No profile = always starts

  worker:
    image: myworker
    profiles: ["full", "backend"]

  ml-engine:
    image: ml-engine
    profiles: ["full", "ml"]

  monitoring:
    image: grafana
    profiles: ["full", "debug"]
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: docker compose up — starts only services without profiles (api).."
⚡ 60-Second Elevator Pitch Talking Points
  • docker compose up — starts only services without profiles (api).
  • docker compose --profile backend up — starts api + worker.
  • docker compose --profile full up — starts everything.
⛔ 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 Docker Compose file 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 Docker Compose file 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 Docker Compose file 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 Docker Compose file 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 →