The current container test masks a unit part of system, ie shipped through /var/lib/systemd, not something living in /etc/systemd/system.
The override mechanism do not work for files living in /etc/systemd/system. The system-manager files living there are generated by
|
"systemd/system".source = |
. Everything is symlinked in
systemd/system. On the module system boundary, we do not have access to the individual unit files, hence, we're unable to set them to
replaceExisting.
A proper fix likely entails listing all the unit files and explicitely list them in environment.etc with replaceExisting set to true.
The current container test masks a unit part of system, ie shipped through /var/lib/systemd, not something living in /etc/systemd/system.
The override mechanism do not work for files living in /etc/systemd/system. The system-manager files living there are generated by
system-manager/nix/modules/systemd.nix
Line 224 in e460edf
systemd/system. On the module system boundary, we do not have access to the individual unit files, hence, we're unable to set them toreplaceExisting.A proper fix likely entails listing all the unit files and explicitely list them in
environment.etcwith replaceExisting set to true.