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).
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."
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"
- 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.
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 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. -
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 ignoresSIGTERMsignals, causing unclean 10s timeouts. - 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.
- 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.