A container won't start
Diagnoses why a container fails to start or exits immediately, covering an unreachable daemon, an out-of-memory kill, and a clean-but-unexpected exit, and routes to the right fix or the container's own logs.
Run this
Read-onlyCheck whether the Docker daemon is reachable at all
docker infoMatched against this step's known patterns to pick the next step.
View full flow
- view_logskind: recipe_ref
- outcome: success → logs_reviewed
- default → unknown_failure
- oom_killedkind: outcome
- check_daemon (entry)kind: diagnostic
- match "Cannot connect to the Docker daemon" → start_daemon
- match "permission denied" → daemon_permission_error
- default → inspect_exit_reason
- start_daemonkind: recipe_ref
- outcome: success → daemon_started
- default → unknown_failure
- logs_reviewedkind: outcome
- daemon_startedkind: outcome
- exited_cleanlykind: outcome
- unknown_failurekind: outcome
- inspect_exit_reasonkind: diagnostic
- match "OOMKilled=true" → oom_killed
- match "ExitCode=0" → exited_cleanly
- default → view_logs
- daemon_permission_errorkind: outcome