hive: install container@.service on every hive, so agents created with nixos-container can start
This commit is contained in:
parent
0370076463
commit
5747c4c325
2 changed files with 16 additions and 1 deletions
|
|
@ -132,6 +132,11 @@ in
|
|||
services.hyperhive.gateway.dns.enable = lib.mkDefault true;
|
||||
services.hyperhive.network.enable = lib.mkDefault true;
|
||||
|
||||
# nixpkgs defaults this to `config.containers != { }`; with no declarative
|
||||
# container the `container@.service` template is missing and every
|
||||
# `nixos-container start` fails with "Unit container@<name>.service not found".
|
||||
boot.enableContainers = true;
|
||||
|
||||
assertions = [
|
||||
{
|
||||
# The pinned claude reaches agents as a bare path, so this
|
||||
|
|
|
|||
|
|
@ -1579,6 +1579,16 @@ let
|
|||
&& bare.services.dnsmasq.enable
|
||||
&& bare.networking.bridges ? hive-br0;
|
||||
}
|
||||
{
|
||||
# `bare` declares no container, so nixpkgs' own default for the option
|
||||
# is false there; `centralToggleOff` is the absence arm.
|
||||
name = "a hive with no declarative container still gets the container@ template its agents start from";
|
||||
ok =
|
||||
bare.containers == { }
|
||||
&& bare.boot.enableContainers
|
||||
&& bare.systemd.services ? "container@"
|
||||
&& !centralToggleOff.boot.enableContainers;
|
||||
}
|
||||
{
|
||||
# The bridge→loopback drop is a unit of its own that loads its own nft
|
||||
# table, so it does not depend on which firewall backend the host runs.
|
||||
|
|
|
|||
Loading…
Reference in a new issue