stocktake 2026-11-20: re-verify 9-page 2026-10-29 stale cohort live; correct nanobot docker/cron drift, camofox host/port claims, dead-pin residual; freshness 0 stale/136 fresh
This commit is contained in:
@@ -3,8 +3,8 @@ title: Recover a Docker service
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-29
|
||||
verified_on: 2026-10-29
|
||||
updated: 2026-11-20
|
||||
verified_on: 2026-11-20
|
||||
tags: [runbook, docker, recovery]
|
||||
sources: []
|
||||
confidence: high
|
||||
@@ -20,6 +20,11 @@ Container shows healthy after recovery probe reboots.
|
||||
## Last successfully used
|
||||
2026-07-22
|
||||
|
||||
> **Re-verified 2026-11-20 (stocktake, procedure only).** `docker ps` as `hermes` on CT460 still
|
||||
> returns permission denied (`/var/run/docker.sock` is `root:docker 0660`) — sudo or SSH to the
|
||||
> owning host remains required. CT201 homepage degradation **persists**: `:8085` answers **502**
|
||||
> locally, `homepage-manager` up but no dashboard container on 8082. Steel remains fully removed
|
||||
> (re-probed CT201/CT333: no containers, no images, no routes).
|
||||
> **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`,
|
||||
|
||||
Reference in New Issue
Block a user