say that the backend env leaf and file are agent-writable, and why that is accepted
This commit is contained in:
parent
75e9e205e3
commit
be3a3af093
1 changed files with 22 additions and 4 deletions
|
|
@ -192,7 +192,10 @@ in
|
|||
read-write for recovery — see `docs/agent-lifecycle/persistence.md`'s "Cross-agent access to
|
||||
state"), so this credential is reachable by nothing but this agent
|
||||
and the host. Permissions should be `0600`, owned by the agent's
|
||||
unix user. Loaded with a leading `-` (optional `EnvironmentFile`),
|
||||
unix user. Whatever owner it was installed with, the file becomes
|
||||
agent-owned at the container's next boot, so the agent can rewrite it;
|
||||
it is no boundary the agent can't cross until the swarm secret store
|
||||
replaces the file. Loaded with a leading `-` (optional `EnvironmentFile`),
|
||||
so a path that doesn't exist yet — an operator setting this option
|
||||
before creating the file, or a fresh host rebuild before state is
|
||||
restored — makes systemd skip it rather than refuse to start the
|
||||
|
|
|
|||
Loading…
Reference in a new issue