Root cause of the long-standing cloud_provider: steel residue: the 2026-07-30 rollback disabled the browser-steel plugin and set browser.engine: camofox but left browser.cloud_provider: steel in config.yaml. The split config was inert-but-wrong, so it survived ~3 months of audits unnoticed. Corrects pages that still described Steel as present, running or configured: - systems/browser-backend.md (incl. gateway-restart env-var note) - comparisons/steel-vs-camoufox.md, comparisons/camoufox-vs-chrome.md - decisions/rollback-steel-to-camofox.md, decisions/index.md - infrastructure/docker-services.md, infrastructure/tailscale.md, infrastructure/hosts.md - systems/homepage-dashboard.md, systems/scheduled-tasks.md - concepts/browser-automation.md, runbooks/recover-docker-service.md - current-state.md, index.md, agents/nanobot.md - log.md (dated entry; supersedes the 00:3x audit's 'endpoint dark' wording) Also restores the Ignis compose row in infrastructure/docker-services.md, which the 2026-10-11 revision dropped (verified: /home/hermes/docker/ignis/docker-compose.yml exists and the ignis container is Up on CT460). Co-Authored-By: Hermes <hermes@local>
37 lines
1.6 KiB
Markdown
37 lines
1.6 KiB
Markdown
---
|
|
title: Recover a Docker service
|
|
type: runbook
|
|
status: active
|
|
created: 2026-07-22
|
|
updated: 2026-10-29
|
|
verified_on: 2026-10-29
|
|
tags: [runbook, docker, recovery]
|
|
sources: []
|
|
confidence: 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** is **not a recovery case** — it was fully removed on 2026-10-29 (plugin,
|
|
> containers, images, network, project dir and Tailscale Serve routes deleted on CT201 and CT333), so
|
|
> there is no service to bring back. The browser backend is Camofox on CT460; see
|
|
> [[systems/browser-backend]] and [[decisions/rollback-steel-to-camofox]].
|