stocktake 2026-11-05: fix skills-index generator divergence at the root; correct Docker + Tailscale drift against live probes

ROOT CAUSE FIXED - systems/skills-index.md had TWO WRITERS:
the repo wiki-maintain.sh (302 skills / 68 categories) and the stale
~/.hermes/scripts/wiki-maintain.sh (mtime 2026-08-17, 349 skills / 26
categories - it used Path.rglob() and counted the parked .archive/ tree) were
different scripts with different generators, and wiki-maintenance/SKILL.md
line 569 pointed the 23:59 nightly audit at the stale path while the 03:00
stocktake ran the repo path. Each job overwrote the other's page; neither
raised an error. The stale copy is now a delegating wrapper with no generator
logic, and the repo script gained --no-build so the wrapper honours the old
interface without a second generator. Verified by execution.

Live-probe corrections:
- infrastructure/docker-services.md: CT200 61 running / 68 total (was 62);
  worldmonitor-seeder-scheduled does not exist on ANY host (zero 'seeder'
  matches across CT200/201/333/460); CT333 first container renamed again
  (nostalgic_leavitt -> flamboyant_mahavira); CT201 20/26, CT460 1/1,
  CT1001 1/9.
- infrastructure/tailscale.md: node table verified programmatically - 52 rows
  vs 52 live IPv4 peers, no live peer missing, no orphan row, every
  online/offline state matching. conduit 59d->60d, ubuntu-server-xfce
  75d->76d. Serve table still matches tailscale serve status exactly.
- infrastructure/hosts.md: skills figure corrected to 302 / 68 categories.
- index.md: skills-index bullet refreshed to the 2026-11-05 figures.

New incident: incidents/2026-11-05-skills-index-generator-divergence.md
(closes the still-open item on the 2026-08-15 skills-index drift incident).

Freshness: 0 stale / 123 fresh / 3 no-date of 126 pages.
This commit is contained in:
Tony0410
2026-11-05 05:55:45 +08:00
parent 20aa11b0c4
commit 2f3fc9952b
11 changed files with 722 additions and 457 deletions
+23 -24
View File
@@ -3,8 +3,8 @@ title: Docker Services
type: infrastructure
status: mixed
created: 2026-07-22
updated: 2026-11-04
verified_on: 2026-11-04
updated: 2026-11-05
verified_on: 2026-11-05
confidence: high
tags: [docker, homelab, infrastructure]
sources: [raw/configs/hermes-config-sanitized.txt, live-probe]
@@ -20,31 +20,30 @@ Docker runs on **four hosts**, and CT460's socket is not readable by the agent u
| Host | Access | Containers running |
|---|---|---|
| CT200 `docker` (`100.96.150.69`) | `pct exec 200 -- docker ps` via PVE | **62** — main Docker host (**re-verified 2026-11-04**) |
| CT201 `runtipi` (`100.96.244.39`) | `pct exec 201 -- docker ps` via PVE | **20** — Runtipi stack: `audiobookshelf`, `calibre-web`, `code-server`, `cyberchef`, `duplicati`, `filebrowser`, `flaresolverr`, `gotify`, `homarr`, `homebox`, `homepage-manager`, `it-tools`, `linkwarden`, `linkwarden-db`, `mealie-1`, `ntfy`, `runtipi`, `runtipi-db`, `syncthing`, `transmission` (**verified 2026-10-31**) |
| CT333 `clawtest` (`100.122.189.81`) | `pct exec 333 -- docker ps` via PVE | **8** — `nostalgic_leavitt`, `community-spark`, `readlater-extraction-worker`, `readlater`, `kokoro-tts`, `edge-tts`, `gotify`, `onecli-postgres-1`. The `steel-browser` container and its image were **removed 2026-10-29**; `thirsty_payne` was **replaced 2026-11-02** by `nostalgic_leavitt` (`ghcr.io/github/github-mcp-server`, created 2026-11-02) |
| CT1001 `docker-01` (`100.121.12.31`, **on `m93p`**) | `pct exec 1001 -- docker ps` via `m93p` | **1** — `sshwifty`. **Added 2026-10-31** — a fourth Docker host, previously undocumented |
| CT460 `hermes` | `pct exec 460 -- docker ps` **as root** from the PVE host — socket is `root:docker srw-rw----`, the `hermes` user is not in group `docker` (its own `docker ps` → `permission denied while trying to connect to the docker API`) | `ignis` — **running** (`Up 4 days`, `ignis-subpath:0.8.9`, `0.0.0.0:8080->8080/tcp`), re-verified 2026-11-04 |
| CT200 `docker` (`100.96.150.69`) | `pct exec 200 -- docker ps` via PVE | **61** running / 68 total — main Docker host (**re-verified 2026-11-05**) |
| CT201 `runtipi` (`100.96.244.39`) | `pct exec 201 -- docker ps` via PVE | **20** running / 26 total — Runtipi stack: `audiobookshelf`, `calibre-web`, `code-server`, `cyberchef`, `duplicati`, `filebrowser`, `flaresolverr`, `gotify`, `homarr`, `homebox`, `homepage-manager`, `it-tools`, `linkwarden`, `linkwarden-db`, `mealie-1`, `ntfy`, `runtipi`, `runtipi-db`, `syncthing`, `transmission` (**re-verified 2026-11-05**) |
| CT333 `clawtest` (`100.122.189.81`) | `pct exec 333 -- docker ps` via PVE | **8** running / 9 total — `flamboyant_mahavira`, `community-spark`, `readlater-extraction-worker`, `readlater`, `kokoro-tts`, `edge-tts`, `gotify`, `onecli-postgres-1`. The `steel-browser` container and its image were **removed 2026-10-29**; `thirsty_payne` → `nostalgic_leavitt` (2026-11-02) → **`flamboyant_mahavira`** (2026-11-04) — all `ghcr.io/github/github-mcp-server`, created 2026-11-04T10:53:53Z |
| CT1001 `docker-01` (`100.121.12.31`, **on `m93p`**) | `pct exec 1001 -- docker ps` via `m93p` | **1** running / 9 total — `sshwifty`. **Added 2026-10-31** — a fourth Docker host, previously undocumented |
| CT460 `hermes` | `pct exec 460 -- docker ps` **as root** from the PVE host — socket is `root:docker srw-rw----`, the `hermes` user is not in group `docker` (its own `docker ps` → `permission denied while trying to connect to the docker API`) | `ignis` — **running** (`Up 5 days`, `ignis-subpath:0.8.9`, `0.0.0.0:8080->8080/tcp`), re-verified 2026-11-05 |
## CT200 live inventory (re-verified 2026-11-04, 62 containers)
`8mblocal`, `apprise-api`, `audiobookshelf`, `chromadb`, `edge-tts`, `emulatorjs`, `excalidraw-backend`, `excalidraw-frontend`, `filebrowser`, `filebrowser1`, `flaresolverr`, `guacamole-guacamole-1`, `guacamole-guacd-1`, `guacamole-postgres-1`, `homarr`, **`ignis-ignis-1`**, `jellyfin`, `khoj-database-1`, `khoj-sandbox-1`, `khoj-search-1`, `khoj-server-1`, `kokoro-tts`, `libre-closet`, `lobe-chat`, `mycompose-db-1`, `mycompose-saas-1`, `nc_app_context_agent`, `nc_app_talk_bot_ai`, `nextstep-app`, `nextstep-db`, `nextstep-scheduler-1`, `onlyoffice-docserver`, `open-webui`, `overtchat-app`, `overtchat-redis`, `overtchat-searxng`, `portainer`, `portkey-gateway-web-1`, `postgres-newsku`, `prowlarr`, `qbittorrent`, `quickdrop`, `react-resume-client-1`, `readlater`, `readlater-extraction-worker`, `redis-cache`, `save-restricted-bot`, `searxng`, `secret-santa-app`, `sshwifty`, `telegram-bot-api`, `tgvideo-bot`, `tt-rss-app-1`, `tt-rss-db-1`, `tt-rss-updater-1`, `tt-rss-web-nginx-1`, `watchtower`, `worldmonitor`, **`worldmonitor-seeder-scheduled`**, `worldmonitor-redis`, `worldmonitor-redis-rest`, `ytdlp-web-player`.
## CT200 live inventory (re-verified 2026-11-05, 61 running / 68 total)
`8mblocal`, `apprise-api`, `audiobookshelf`, `chromadb`, `edge-tts`, `emulatorjs`, `excalidraw-backend`, `excalidraw-frontend`, `filebrowser`, `filebrowser1`, `flaresolverr`, `guacamole-guacamole-1`, `guacamole-guacd-1`, `guacamole-postgres-1`, `homarr`, **`ignis-ignis-1`**, `jellyfin`, `khoj-database-1`, `khoj-sandbox-1`, `khoj-search-1`, `khoj-server-1`, `kokoro-tts`, `libre-closet`, `lobe-chat`, `mycompose-db-1`, `mycompose-saas-1`, `nc_app_context_agent`, `nc_app_talk_bot_ai`, `nextstep-app`, `nextstep-db`, `nextstep-scheduler-1`, `onlyoffice-docserver`, `open-webui`, `overtchat-app`, `overtchat-redis`, `overtchat-searxng`, `portainer`, `portkey-gateway-web-1`, `postgres-newsku`, `prowlarr`, `qbittorrent`, `quickdrop`, `react-resume-client-1`, `readlater`, `readlater-extraction-worker`, `redis-cache`, `save-restricted-bot`, `searxng`, `secret-santa-app`, `sshwifty`, `telegram-bot-api`, `tgvideo-bot`, `tt-rss-app-1`, `tt-rss-db-1`, `tt-rss-updater-1`, `tt-rss-web-nginx-1`, `watchtower`, `worldmonitor`, `worldmonitor-redis`, `worldmonitor-redis-rest`, `ytdlp-web-player`.
**Re-verified 2026-11-04 — 61 → 62 containers, one addition.** A set-wise diff against live
`docker ps --format '{{.Names}}'` on CT200 shows **exactly one container live but absent from the previous list:
`worldmonitor-seeder-scheduled`** (image `worldmonitor:latest`, `Up 29 minutes`, **status `unhealthy`**). Every
other name in the list above is confirmed live, and **no listed container has disappeared**. Note the seeder's
**new** name — the 2026-11-01 correction removed a `worldmonitor-seeder-fast` entry as "not running", and live
`docker ps -a --filter name=worldmonitor` now shows four worldmonitor containers: `worldmonitor` (`Up 4 days`,
healthy), **`worldmonitor-seeder-scheduled`** (`Up 29 minutes`, **unhealthy**), `worldmonitor-redis` and
`worldmonitor-redis-rest` (`Up 4 days`). The `worldmonitor-seeder-fast` container **does not exist at all** —
not even stopped (`docker ps -a` lists only the four above), so the old entry was correctly removed and the seeder
has since been redeployed under a new name. **Watch item:** `worldmonitor-seeder-scheduled` is reporting
**unhealthy** — worth a look if it does not clear.
**Re-verified 2026-11-05 — 61 → 61 running, seeder entry removed.** A set-wise diff against live
`docker ps --format '{{.Names}}'` on CT200 shows **no container live but absent from the list above**, and
**no listed container has disappeared**. The `worldmonitor-seeder-scheduled` entry recorded on 2026-11-04 as
"unhealthy" **does not exist on any host** — verified with `docker ps -a --filter name=seeder` across CT200,
CT201, CT333 and CT460, all of which return **zero** matches. Live CT200 now shows exactly three worldmonitor
containers: `worldmonitor` (`Up 5 days`, **healthy**), `worldmonitor-redis` (`Up 5 days`) and
`worldmonitor-redis-rest` (`Up 5 days`). There is **no seeder container and no worldmonitor-seeder cron job**
anywhere in the estate — the 2026-11-04 "watch item" was a transient container that has since been removed.
**Correction on record:** the earlier `worldmonitor-seeder-fast` → `worldmonitor-seeder-scheduled` rename
narrative did not reflect a durable redeploy; the seeder is simply absent now.
**CT333 container set — `thirsty_payne` → `nostalgic_leavitt` (2026-11-04).** Live CT333 `docker ps` returns 8
running containers, and the name that had replaced `adoring_jemison` on 2026-11-01 has itself been replaced:
`nostalgic_leavitt` (image `ghcr.io/github/github-mcp-server`, **created 2026-11-02T17:01:17Z**, `Up 29 hours`).
The count is unchanged at 8 and the other seven names are identical. A ninth container, `qdrant`
**CT333 container set — `nostalgic_leavitt` → `flamboyant_mahavira` (2026-11-05).** Live CT333 `docker ps` returns 8
running containers, and the name that had replaced `thirsty_payne` on 2026-11-04 has itself been replaced:
`flamboyant_mahavira` (image `ghcr.io/github/github-mcp-server`, **created 2026-11-04T10:53:53Z**). The count is
unchanged at 8 and the other seven names are identical. A ninth container, `qdrant`
(`qdrant/qdrant`), exists but is **stopped** (`Exited (143) 4 months ago`) — it is not in the running count and
is not listed above. **Docker generates these random names for compose-less containers, so repeated renames are
normal — the reliable check is always the live set, never the recorded name.**