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
|
|
@ -1192,9 +1192,15 @@ in
|
|||
// lib.optionalAttrs publishes (
|
||||
storeRetry.serviceConfig
|
||||
// {
|
||||
RestartSec = 15;
|
||||
LoadCredential = lib.attrNames storeFiles;
|
||||
TimeoutStartSec = 120;
|
||||
# Bounds one run, 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.
|
||||
# What a killed run left is picked up by the next one.
|
||||
TimeoutStartSec = 30;
|
||||
RestartSec = 15;
|
||||
RestartSteps = 3;
|
||||
RestartMaxDelaySec = 120;
|
||||
}
|
||||
);
|
||||
environment = lib.optionalAttrs publishes (
|
||||
|
|
@ -1281,6 +1287,11 @@ in
|
|||
// lib.optionalAttrs publishes {
|
||||
RuntimeDirectory = "swarm-authelia-bridge";
|
||||
LoadCredential = lib.attrNames storeFiles;
|
||||
# The secret fetch is part of the start job, which is in the
|
||||
# container's boot wait: a store that never answers ends it here
|
||||
# and not at the 90 s default, which is over the container's
|
||||
# one-minute start limit.
|
||||
TimeoutStartSec = 10;
|
||||
};
|
||||
environment = {
|
||||
SWARM_AUTHELIA_BRIDGE_SOCKET = bridgeSocket;
|
||||
|
|
|
|||
Loading…
Reference in a new issue