⚡ ~/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 80 of 159 in Docker & Containers
Staff SRE / Principal Architect [L3] Docker Must enable BuildKit Staff SRE Scenario [L3]
🎯 Target Role / Context: Docker Scenario #81 (L3) · Must enable BuildKit

Q: You are running a sidecar monitoring agent alongside your main application container using Docker Compose. The agent needs to see all the processes running inside the main application container using `ps aux`. By default, it can only see its own processes. How do you solve this?

By default, every Docker container gets its own isolated PID namespace, meaning each container can only see its own processes (its PID 1 and descendants).

#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: PID namespace sharing between containers.. 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: PID namespace sharing between containers.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Production Solution & Architecture

By default, every Docker container gets its own isolated PID namespace, meaning each container can only see its own processes (its PID 1 and descendants). To allow the monitoring sidecar to observe the main application's processes, you must share the PID namespace between the two containers using the pid option: With pid: "service:app", the monitor container joins the PID namespace of the app container and can see all of its processes via ps aux or /proc. In plain Docker CLI: docker run --pid=container:main-app monitoring-agent.

services:
  app:
    image: myapp
    container_name: main-app

  monitor:
    image: monitoring-agent
    pid: "service:app"
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: By default, every Docker container gets its own isolated PID namespace, meaning each container can only see its own processes (its."
⚡ 60-Second Elevator Pitch Talking Points
  • Immediate Triage: By default, every Docker container gets its own isolated PID namespace, meaning each container
  • 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 running sidecar monitoring 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 running sidecar monitoring 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 running sidecar monitoring 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 running sidecar monitoring 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 →