Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to use non-glibc nss modules when setting services.nscd.package = pkgs.unscd; #193535

Closed
flokli opened this issue Sep 29, 2022 · 2 comments

Comments

@flokli
Copy link
Contributor

flokli commented Sep 29, 2022

I tried to give unscd a go, and set services.nscd.package = pkgs.unscd;.

While unscd successfully starts up as nscd.service, it seems it's not able to discover the NSS modules we point it to via LD_LIBRARY_PATH.

Repro:

Configure your system like this:

{
  services.nscd.package = pkgs.unscd;
}

Try to run a query requiring a non-glibc NSS module:

$ systemd-run --pty --property=Type=oneshot --property=DynamicUser=yes --property=User=iamatest whoami
/run/current-system/sw/bin/whoami: cannot find name for user ID 63915

If I drop the services.nscd.package option, the call works:

$ systemd-run --pty --property=Type=oneshot --property=DynamicUser=yes --property=User=iamatest whoami
Running as unit: run-u882.service
Press ^] three times within 1s to disconnect TTY.
iamatest

cc @erikarvstedt @Ericson2314

@flokli
Copy link
Contributor Author

flokli commented Oct 13, 2022

6eed70c from #194916 provides a reproducer for this. I think it's a general unscd problem.

@flokli
Copy link
Contributor Author

flokli commented Oct 13, 2022

I'm tempted to say there's nothing to be done for nixpkgs here, so we should either see if upstream fixes this, or switch to an alternative.

@flokli flokli closed this as completed Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant