Closed Yasso9 closed 1 week ago
I need more info to do anything about this, otherwise I'll just close the issue. What's the config?
Closing unless more info is given.
@rasmus-kirk Apologies for pinging you; I'm not sure if you'll be notified otherwise since the issue is closed.
I receive the same error when I simply add the nixarr
module to my flake.nix
without actually adding any nixarr
configuration options to my configuration.nix
.
I haven't yet successfully configured nixarr
, but I think this default behavior by itself is confusing to the user since simply adding the module without adding a configuration should cause no effect (at least, I can't think of other NixOS modules that have such effects).
Sorry for the late response and my bad explanation
I have indeed the same issue as @raj-magesh, but I managed to find a workaround by just having nixarr.enable = true;
in the config where I do not use nixarr.
While the solution is simple, I still think it might be a bad default to error out when no configuration is defined, since it surprises the user.
I'll reopen this then
Should be fixed upstream in new version of the von submodule
When I add nixarr as input of me nix flake, I have the error : "The option vpnnamespaces is used but not defined." when I rebuild my flake.