noe/pihole-flake
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

modules(pihole-container): add option for enabling user lingering (not wired)

Browse source
This commit is contained in:
Christopher Bacher 2022-10-22 15:47:37 +02:00
parent c8e603fd29
commit 9238520b65
1 changed files with 15 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
modules/pihole-container.factory.nix
View file

@ -2,6 +2,7 @@
inherit (util) collectAttrFragments accessValueOfFragment toEnvValue;
cfg = config.services.pihole;
hostUserCfg = config.users.users.${cfg.hostConfig.user};
systemTimeZone = config.time.timeZone;
defaultPiholeVolumesDir = "${config.users.users.${cfg.hostConfig.user}.home}/pihole-volumes";
@ -58,6 +59,18 @@ in rec {
'';
};
enableLingeringForUser = mkOption {
type = with types; oneOf [ bool (enum [ "suppressWarning" ]) ];
description = ''
If true lingering (see `loginctl enable-linger`) is enabled for the host user running pihole.
This is necessary as otherwise starting the pihole container will fail if there is no active session for the host user.
If false a warning is printed during the build to remind you of the issue.
Set to "suppressWarning" if the issue is solved otherwise or does not apply.
'';
default = false;
};
containerName = mkOption {
type = types.str;
description = ''
@ -292,10 +305,8 @@ in rec {
config = mkIf cfg.enable {
assertions = let
hostUserCfg = config.users.users.${cfg.hostConfig.user};
in [
{ assertion = hostUserCfg ? "subUidRanges" && hostUserCfg ? "subGidRanges";
assertions = [
{ assertion = length hostUserCfg.subUidRanges > 0 && length hostUserCfg.subGidRanges > 0;
message = ''
The host user most have configured subUidRanges & subGidRanges as pihole is running in a rootless podman container.
'';