R-858 closed (agent v0.142.1, ruling 95): the Docker step restarts the socket users; incident evidence; STATUS; report addendum

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-04 18:35:40 +02:00
parent 242f0a15d5
commit 6b820143f8
12 changed files with 76 additions and 5 deletions
@@ -778,6 +778,15 @@ its length, and both fixes cost something the household would notice — operato
 83. **Next: the tunnel status (R-841), the host fast lane (`11` §8 step 3), and other OS-update improvements.**
    *Operator ruling 2026-10-04 ~12:20.*

+### 2026-10-04 (~18:00) — operator ruling after the R-858 incident
+
+95. **A Docker engine step restarts the containers that mount the Docker socket** (R-858): after every step that
+    installed something, the wrapper restarts ONLY those containers (today `felhom-controller` and `traefik`, ~10 s;
+    apps untouched, the engine untouched), and the health rule checks that the controller reaches Docker from inside its
+    container. **Rejected:** mounting a socket folder instead of the file (cleaner, but it changes Docker's config, the
+    controller templates and the golden on every box). Until the fix is released, the demo boxes' root-owned ring-0
+    Docker mark is OFF (no unsigned step). *Operator ruling 2026-10-04 ~18:00.*
+
 ### 2026-10-04 (evening) — decided by CC unattended — operator may reverse (System page / Docker / crash-restart brief)

 90. **How does a box tell a crash boot from a clean one?** Options: (a) `pstore` — measured on demo-hp: `efi_pstore` is on,