nixBuilds none: turn the container's own nix-daemon socket and service off
This commit is contained in:
parent
5485151ba6
commit
f930571e38
1 changed files with 30 additions and 0 deletions
|
|
@ -200,6 +200,10 @@ to socket at '/nix/var/nix/daemon-socket/socket'`, which names the cause. The
|
|||
agent's `/nix/store` and its read-only nix database stay bound, so store
|
||||
paths already there stay readable; only a realisation of a new path, or any
|
||||
`nix` command that needs the daemon, fails.
|
||||
The agent's own NixOS config turns its `nix-daemon` socket and service off in
|
||||
this mode: the tmpfs is writable, so the unit would otherwise listen on it.
|
||||
Under `host` the directory is the host's read-only bind, which the socket
|
||||
unit's `ConditionPathIsReadWrite` rejects, so that unit never starts.
|
||||
|
||||
The mode reaches the container as `privateUsers` does: the swarm builder reads
|
||||
the option from the evaluated config into the agent's closure record
|
||||
|
|
|
|||
Loading…
Reference in a new issue