The original title is "Debugging Containers From the Terminal: A Practical Docker CLI Workflow"

Short summary

Methodical Docker debugging workflow: check container status with `docker ps -a` and read exit codes (0=clean, 137=OOM-killed, 143=graceful stop), then read logs with `docker logs --tail`, inspect state with `docker inspect --format`, and shell in as last resort. Follow this sequence from cheapest to most involved checks to avoid wrong conclusions under pressure.

• •Start with `docker ps -a`: exit code tells you the root cause without guessing
• •Read logs with `docker logs --tail 100` to find the crash cause before rebuilding
• •Use `docker inspect --format` to confirm OOMKilled status, mounts, and restart loops

Generated with AI, which can make mistakes.