vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

ops(pfi-pteradactyl): docker.io/containerd upgraded (manual dockerd + wings restart); docs

Browse Source
This commit is contained in:
vh
2026-10-05 14:18:57 -07:00
parent 58bd802872
commit 3429b5c55d
3 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/runbooks/fleet-guest-patch-2026-10-05.md
+2 -2
View File
@@ -125,8 +125,8 @@ bouncer failing closed on slow LAPI answers. Self-cleared.
`/health` after boot (startup, not a fault); wings on pfi-pteradactyl restores the running game server by itself.
- ⚠ For every held engine bump: if `/etc/docker/daemon.json` has `live-restore: true`, an engine upgrade without a reboot leaves
containers that bind-mount `/var/run/docker.sock` on a stale socket. Restart them afterwards (see servers/ana-docker/README.md).
- Docker engine bumps still held on nh3-docker (29.4.1; the bus + NH3 DNS), esh-docker-vm (29.4.1; ESH DNS + homepage
wedge risk) and pfi-pteradactyl (docker.io; the live game server). Done 10-05: ana-docker → 29.8.2 (bookworm repo),
- Docker engine bumps still held on nh3-docker (29.4.1; the bus + NH3 DNS) and esh-docker-vm (29.4.1; ESH DNS + homepage
wedge risk). pfi-pteradactyl's docker.io upgraded 10-05 1418 (needed a manual dockerd restart plus a wings restart). Done 10-05: ana-docker → 29.8.2 (bookworm repo),
pfi-gx10 → 29.6.2, and ~1410–1415 esh-ml1, nh3-ml1, nh3-dev, corviduo-dev → 29.8.2, each verified (same containers,
health endpoints, the embedding routes back on their primaries). NVIDIA/CUDA holds on the ml1s were kept.
- fv-ml1: ZFS 2.3.9, nvidia-container-toolkit 1.20, and a kernel with an NVIDIA driver that builds on it.