-
Notifications
You must be signed in to change notification settings - Fork 81
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
nix daemon doesn't have access to nix binaries itself #82
Comments
It uses the official installer, so whatever the official systemd service does is what this action uses. |
So it might be a bug in the installer? |
It doesn't seem to have Nix binaries available: https://github.com/NixOS/nix/blob/master/misc/systemd/nix-daemon.service.in |
NixOS comes with the following overrides:
|
Hmmh, I wonder if at least the unit files provided by the multi-user installer should ensure In any case, that's a bug in the installer, not the GH action - so closing here. Thanks for the digging! |
I opened NixOS/nix#4902 upstream. |
just ran into this @flokli how did you solve it? I guess I can use full path to nix executable when creating to |
The answer is probably not gonna help much - I switched my workflows to dedicated CI runners and have Nix already installed on them (via NixOS) 😉 |
Thanks. I’ve got a self hosted NixOS based runner but also need to run some odd jobs on macOS and can’t be bothered to setup a self hosted runner for it. |
I invoke some nix commands in a script that
post-build-hook
inextra_nix_config
is pointing to.The
post-build-hook
is executed via the nix-daemon, as the installer uses a multi-user installation.On NixOS, the nix-daemon system units are configured to have config.nix.package in
$PATH
, so this works.It seems this isn't the case with this action -
nix-build
,nix
etc. are not in$PATH
.The text was updated successfully, but these errors were encountered: