Files
nixos-setup/modules
Hermenix a8bc08de43 container-services: queue the env-reload restart instead of blocking on it
The env-reload unit is a oneshot whose ExecStart was a blocking
systemctl restart of the group unit. When the stack's cold start failed
transiently (container-services-buzz on minipc1, where buzz-relay-1 came
up unhealthy and compose exited 1), the group unit recovered on its own a
few seconds later through its own Restart=on-failure, but the reload unit
had already exited 1 with no restart policy and stayed failed until the
next env file write.

The trigger unit should queue the restart, not own the health of the whole
stack: pass --no-block. Real failures still surface on the group unit,
which carries Restart=on-failure and the start limit and is what the fleet
scan reports.
2026-11-09 15:04:30 +00:00
..
2026-10-26 16:18:48 -04:00
2026-10-16 15:07:11 -04:00
2026-10-16 15:07:11 -04:00
2026-11-05 15:21:01 -05:00
2026-10-26 16:18:48 -04:00
…
2026-11-05 15:21:01 -05:00
2026-04-13 16:39:18 -04:00
2026-10-13 19:52:54 -04:00