Q: A container is running but your app inside it crashed. Docker shows the container as "Up." Why?
The container's PID 1 (init process) is still running but the app process (a child) crashed. If using shell scripts as entrypoint, the sh...
#Docker #Docker #L2 #Containers #Linux
🎙️ Candidate Opening & Architectural Context
""When containerizing our microservices stack, container lifecycle and resource management were critical. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
The container's PID 1 (init process) is still running but the app process (a child) crashed. If using shell scripts as entrypoint, the shell is still alive even after the app it started dies. Fix: use exec in shell scripts to replace the shell with the app process: exec node server.js. Or use a proper init system in the container. Add a healthcheck to detect app failure.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: The container's PID 1 (init process) is still running but the app process (a child) crashed. If using shell scripts as entrypoint,."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: The container's PID 1 (init process) is still running but the app process (a child) crashed. If
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement