a9e3ec1d6e
In contrast to `.service`-units, it's not possible to declare an `overrides.conf`, however this is done by `generateUnits` for `.nspawn` units as well. This change breaks the build if you have two derivations configuring one nspawn unit. This will happen in a case like this: ``` nix { pkgs, ... }: { systemd.packages = [ (pkgs.writeTextDir "etc/systemd/nspawn/container0.nspawn" '' [Files] Bind=/tmp '') ]; systemd.nspawn.container0 = { /* ... */ }; } ``` |
||
---|---|---|
.. | ||
loader | ||
binfmt.nix | ||
emergency-mode.nix | ||
grow-partition.nix | ||
initrd-network.nix | ||
initrd-ssh.nix | ||
kernel.nix | ||
kernel_config.nix | ||
kexec.nix | ||
luksroot.nix | ||
modprobe.nix | ||
networkd.nix | ||
pbkdf2-sha512.c | ||
plymouth.nix | ||
resolved.nix | ||
shutdown.nix | ||
stage-1-init.sh | ||
stage-1.nix | ||
stage-2-init.sh | ||
stage-2.nix | ||
systemd-lib.nix | ||
systemd-nspawn.nix | ||
systemd-unit-options.nix | ||
systemd.nix | ||
timesyncd.nix | ||
tmp.nix |