Q: A container exits immediately after starting. How do you debug it?
docker logs <container-id> — read why it exited. Use docker run -it <image> sh to start interactively. Check the entrypoint/cmd. Common c...
#Docker #Docker #L1 #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
docker logs — read why it exited. Use docker run -it to start interactively. Check the entrypoint/cmd. Common cause: the main process exits (e.g., a script returns 0), so the container stops. Containers live only as long as their PID 1 runs.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: docker logs — read why it exited. Use docker run -it sh to start interactively. Check the entrypoint/cmd. Common cause: the main."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: docker logs — read why it exited. Use docker run -it sh to start interactively. Check the ent
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement