From 77d8988b7b6374b0cc0aaa2f16d68c4b2d81a55f Mon Sep 17 00:00:00 2001 From: Maximilian Bosch Date: Sat, 21 Dec 2019 17:07:38 +0100 Subject: [PATCH] nixos/systemd-nspawn: use `config.systemd.package` When using a modified systemd-package (e.g. to test a patch), it's recommended to use the `systemd.package`-option to avoid rebuilding all packages that somehow depend on systemd. With this change, the modified package is also used by `systemd-nspawn@` units. --- nixos/modules/system/boot/systemd-nspawn.nix | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nixos/modules/system/boot/systemd-nspawn.nix b/nixos/modules/system/boot/systemd-nspawn.nix index 3ddd45b1348..1e2435e36f0 100644 --- a/nixos/modules/system/boot/systemd-nspawn.nix +++ b/nixos/modules/system/boot/systemd-nspawn.nix @@ -126,7 +126,7 @@ in { systemd.services."systemd-nspawn@".serviceConfig.ExecStart = [ "" # deliberately empty. signals systemd to override the ExecStart # Only difference between upstream is that we do not pass the -U flag - "${pkgs.systemd}/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth --settings=override --machine=%i" + "${config.systemd.package}/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth --settings=override --machine=%i" ]; } ];