Files
agent-estate-wiki/runbooks/recover-docker-service.md
T

1.4 KiB

title, type, status, created, updated, verified_on, tags, sources, confidence
title type status created updated verified_on tags sources confidence
Recover a Docker service runbook active 2026-07-22 2026-10-20 2026-10-20
runbook
docker
recovery
high

Recover Docker service

Procedure

  1. Identify the container.
  2. Inspect status and last 100 log lines.
  3. If unhealthy, restart then re-check.
  4. If still failing, inspect image and mounts.

Verification

Container shows healthy after recovery probe reboots.

Last successfully used

2026-07-22

Verified 2026-10-20 (procedure, not a live recovery). Before running any docker command from CT460, note that the hermes user has no access to /var/run/docker.sock — docker ps returns permission denied while trying to connect to the docker API. Use sudo, or SSH to the host that owns the container. The containers in this estate mostly live on CT201 (runtipi), CT209 (cloudreve) and m93p CT500 (LiteLLM) — not on CT460.

Two live situations this runbook would have been used for in the last week:

  • The CT201 homepage dashboard is degraded — main container removed, asset_proxy.py on 8085 proxying to a dead 8082, and the Tailscale / route returning 502. See systems/homepage-dashboard.
  • The Steel browser service is unreachable (steel.martinwa.org → connection failure). See decisions/rollback-steel-to-camofox.