keep service containers' boot-wait budgets under their start limit, and check it
This commit is contained in:
parent
da0cdda6a4
commit
70b112058a
1 changed files with 553 additions and 9 deletions
|
|
@ -1017,9 +1017,17 @@ in
|
|||
LoadCredential = lib.attrNames storeFiles;
|
||||
# The forge's answers pass through a temp file.
|
||||
PrivateTmp = true;
|
||||
# Each forge call is bounded by curl's own timeouts, and a sealed
|
||||
# store answers on the port and never answers the write.
|
||||
TimeoutStartSec = "3min";
|
||||
# Bounds one attempt, and so the container's boot when the store
|
||||
# accepts a connection and never answers: this unit is in the boot
|
||||
# wait of a container with a one-minute start limit. A killed
|
||||
# attempt is retried with the growing delay below; an attempt
|
||||
# that minted a token and was killed leaves one the next
|
||||
# attempt revokes. The account re-check (`accountRecheckSec`) runs
|
||||
# inside this budget.
|
||||
TimeoutStartSec = 30;
|
||||
RestartSec = 5;
|
||||
RestartSteps = 6;
|
||||
RestartMaxDelaySec = 300;
|
||||
};
|
||||
# `FORGEJO_CUSTOM`, same reason as `forgejo-sso-source` above:
|
||||
# every `forgejo admin` invocation needs it to find the app.ini
|
||||
|
|
|
|||
Loading…
Reference in a new issue