wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,9 +3,9 @@ title: Diagnose Failed Docker Service
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
verified_on: 2026-07-22
|
||||
last_tested: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
last_tested: 2026-10-20
|
||||
confidence: medium
|
||||
tags: [runbook, docker, homelab]
|
||||
sources: []
|
||||
@@ -26,6 +26,15 @@ Diagnose container or compose issues on hosts where Docker is present.
|
||||
- Docker daemon running
|
||||
- Compose file path known for the affected project
|
||||
|
||||
> **Important scoping note, verified 2026-10-20: the `hermes` user is NOT in the `docker` group on
|
||||
> CT460.** `systemctl is-active docker` → `active`, but `docker ps` as `hermes` returns
|
||||
> **`permission denied while trying to connect to the docker API at unix:///var/run/docker.sock`**.
|
||||
> Most Docker services in this estate run on **other hosts** (runtipi CT201, cloudreve CT209,
|
||||
> LiteLLM CT500 on m93p, etc.) where the invoking account does have socket access.
|
||||
> So: on CT460, either use `sudo docker …` or SSH to the host that actually owns the container.
|
||||
> Note also that `systems/homepage-dashboard.md` now records the CT201 stack as **degraded** —
|
||||
> the main dashboard container is gone — which is exactly the symptom this runbook would be used for.
|
||||
|
||||
## Procedure
|
||||
|
||||
### 1. Check Docker daemon state
|
||||
|
||||
Reference in New Issue
Block a user