order the store's readers after its container without wanting it
This commit is contained in:
parent
b1c828dbf8
commit
868c57321c
1 changed files with 37 additions and 28 deletions
|
|
@ -6,6 +6,12 @@
|
|||
# log in to it, and nothing else. The waits on the store's policy units are
|
||||
# ./glue-bao-readers-policy-order.nix's.
|
||||
#
|
||||
# No `Wants=` on the container: it is started by `machines.target` and the
|
||||
# switch's start phase, and a reader's `Wants=` would pull it up mid-switch,
|
||||
# before `activate` has replaced its configuration, on the OLD closure. A
|
||||
# reader that starts before the store costs one failed attempt, retried by
|
||||
# ./lib/store-retry.nix.
|
||||
#
|
||||
# `Wants=` on `swarm-bao-pki`, not `Requires=`: a pki start that fails or is
|
||||
# refused fails each requirer's job with `dependency`, which leaves the reader
|
||||
# inactive rather than failed, so its `Restart=on-failure` never fires. Here
|
||||
|
|
@ -77,10 +83,7 @@ let
|
|||
"swarm-bao-pki.service"
|
||||
"container@${baoCfg.machine}.service"
|
||||
];
|
||||
wants = [
|
||||
"swarm-bao-pki.service"
|
||||
"container@${baoCfg.machine}.service"
|
||||
];
|
||||
wants = [ "swarm-bao-pki.service" ];
|
||||
};
|
||||
};
|
||||
in
|
||||
|
|
|
|||
Loading…
Reference in a new issue