WHOSEPORT
Investigations · guide

Container stopped or restarting

A container that exited, or that Docker keeps restarting. Start from its exit code and last log lines.

Ask

bash
whoseport ask "why is platform-db-1 not running"

What WhosePort checks

  • State, health, exit code and restart count
  • Recent log lines, redacted
  • Published ports and the compose project it belongs to
  • Which services depend on it

Typical root cause

Most often a stopped container nobody restarted, or an entrypoint that fails on a missing setting.

Proposed fix

  • restart_container when the logs show nothing that would make it fail again (approval required)
  • Otherwise a written explanation of the change to make; WhosePort never edits compose files or removes volumes
Approval
Every step that changes your machine is a typed action classed by the policy engine. It waits for your approval in the dashboard, which shows the target, risk and expected effect first. A changed .env file is backed up before it is written. See /docs/policy.

Verification

  • Container running
  • Health check healthy, when the image defines one