-
Notifications
You must be signed in to change notification settings - Fork 6
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
[install script] Could not find service "org.nixos.nix-daemon" in domain for system #407
Comments
Our install script did not call the determinate systems installer, since it detected that nix was installed. I wonder if that one would or could've "repaired" this somehow. Could you try running that installer manually? I think it also has a |
They seem to also have this issue, though the solution there does not work for me. |
Oh, it's just because this was a single-user install. Maybe this is an occasion to fix this? |
That comment is not a TODO to fix, it's just trying to say that we don't abort on errors, since these commands fail in single-user installations, but in that case we just don't have to restart the |
|
It occurred to me, following discussion on the garnix Discord, that we could just put the substituter in the flake.nix of It doesn't work if the user isn't in |
I guess we could have a multi-pronged approach: we try setting it globally, but don't fail if we can't (just issue a warning), and instead hope the flake-specific setting does the trick. |
I think by default users are untrusted. So in a default nix installation this wouldn't work. Also, I think putting the cache into the flake file will mean that nix will ask the user whether these settings should be used. And if the user agrees, nix will also print out a message that these caches are being used every time nix runs. (I think that's how it works, haven't researched this more. But I think we need to look into this before considering this approach.) |
I tried installing garn on an older MacOS machine, which already had an old version of nix installed. I got the following error:
This issue seems relevant.
The text was updated successfully, but these errors were encountered: