Commit Graph
7 Commits
Author SHA1 Message Date
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
ari 17b14b33e5 making sure files will cause a restart 2026-10-03 00:57:28 -04:00
ari df46627173 some security patches + buzz updates 2026-09-20 20:55:17 -04:00
ari beb83f21b3 buz support 2026-09-20 20:13:39 -04:00
ari a7b9273296 new static ip and merge approach 2026-09-16 22:02:04 -04:00
ari 2a2bdd0b4b moving minipc2 services to nix 2026-08-27 15:15:06 -04:00
ari d9b984db7f better cleaner containers 2026-06-28 15:55:16 -04:00