docs(esh-docker-vm): homepage wedge cleared by a VM reboot; record that it needs a manual start afterwards

2026-09-25 06:20:25 -07:00
parent b3bb5512e6
commit e128f5da63
2 changed files with 13 additions and 7 deletions
@@ -97,7 +97,14 @@ state too. Read `/proc/<pid>/task/*/stat` and `sudo cat .../stack` instead
 (`ssh infra-ops@10.0.50.45`, NOPASSWD).

 **Only a VM reboot clears it**, and this VM is ESH's DNS resolver, so the
-reboot is a short ESH-wide DNS outage — schedule it. Root cause not
+reboot is a short ESH-wide DNS outage — schedule it.
+
+⚠ **After the reboot, homepage does NOT come back by itself** if anyone tried
+`docker restart`/`stop` on it first: docker records it as stopped on purpose,
+so `restart: unless-stopped` skips it. Run `docker start homepage`. Measured
+2026-09-25: `qm reboot 100` from esh-pve took 3m18s (the graceful shutdown
+stalls on the wedged process, then proceeds); the VM was unreachable
+0613:44–0616:58 PT; every other container came back unaided. Root cause not
 established; a kernel-side mmap_lock problem is the leading guess, not a
 finding. Moving Homepage to ana-docker (as was done for Uptime Kuma on
 2026-09-21 for the same box's history) would take the dashboard out of this