forked from
lass.pds.lassul.us/superconfig
This repository has no description
sync-containers3: auto-restart autoswitch on failure
A transient GitHub 5xx while resolving the flake at boot used to leave a
container's autoswitch in a failed oneshot state with no retry, silently
running stale config (observed on yellow: the disk-space guard never
updated to the 100 GiB threshold).
Add Restart=on-failure with RestartSec=120s. Since RestartSec is well
above the default StartLimitIntervalSec, the restart rate limiter never
trips, so a transient failure keeps retrying every 2 min and self-heals
once GitHub recovers.
Assisted-by: Claude Code (claude-opus-4-8[1m])
author
lassulus
date
(Jun 20, 2026, 7:10 PM CEST)
commit
6fc8e0f4
6fc8e0f423c1271669587c7432dd8c828c734eca
parent
8ec0532b
8ec0532b7e4e5643bbdfe84c940091160d75ec67
+10
-1
+10
-1
3modules/sync-containers3.nix
+10
-1
3modules/sync-containers3.nix
···
86
86
NIX_REMOTE = "daemon";
87
87
};
88
88
wantedBy = [ "multi-user.target" ];
89
-
serviceConfig.ExecStart = pkgs.writers.writeDash "autoswitch" ctr.startCommand;
89
+
serviceConfig = {
90
+
ExecStart = pkgs.writers.writeDash "autoswitch" ctr.startCommand;
91
+
# keep retrying transient failures (e.g. a GitHub 5xx while
92
+
# resolving the flake at boot) so we self-heal instead of
93
+
# staying silently stale. RestartSec is well above the default
94
+
# StartLimitIntervalSec, so the restart rate limiter never trips
95
+
# and we retry until it succeeds.
96
+
Restart = "on-failure";
97
+
RestartSec = "120s";
98
+
};
90
99
unitConfig.X-StopOnRemoval = false;
91
100
};
92
101
# get rid of stateVersion not set warning;