CodewrightConsequence-aware terminal workflows

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-only

Check whether the Docker daemon is reachable at all

docker info

Matched against this step's known patterns to pick the next step.

View full flow
  • view_logsPending
    kind: recipe_ref
    • outcome: success → logs_reviewed
    • default → unknown_failure
  • oom_killedPending
    kind: outcome
  • check_daemon (entry)In progress
    kind: diagnostic
    • match "Cannot connect to the Docker daemon" → start_daemon
    • match "permission denied" → daemon_permission_error
    • default → inspect_exit_reason
  • start_daemonPending
    kind: recipe_ref
    • outcome: success → daemon_started
    • default → unknown_failure
  • logs_reviewedPending
    kind: outcome
  • daemon_startedPending
    kind: outcome
  • exited_cleanlyPending
    kind: outcome
  • unknown_failurePending
    kind: outcome
  • inspect_exit_reasonPending
    kind: diagnostic
    • match "OOMKilled=true" → oom_killed
    • match "ExitCode=0" → exited_cleanly
    • default → view_logs
  • daemon_permission_errorPending
    kind: outcome