-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Permission denied when trying to update flake.lock #79
Comments
nh doesn't run nix as root, only the activation scripts |
I just want to know if this is the intended behavior, as it requires another command to upgrade. I write a wrapper for the commands and now it work perfectly. |
It's weird behaviour nonetheless |
I'm guessing that's the issue, as flakes are updated by the nix command? |
I know the issue but not the cleanest way to handle it. And my NixOS flake is not owned by root, so I don't need to fix this immediately |
So the temporary fix is changing the ownership of flake.nix and flake.lock? |
I'd say not using nh's |
I am also struggling with this, nh os switch fails whenever I update my flake inputs, shouldn't nh ask for sudo like it does at other times it is required? |
No, because I want to keep the evaluation apart from root |
Do you suggest permanently changing ownership then? |
Running nix flake update as the same user that owns the flake |
I have a similar issue: using agenix the quick and dirty way and putting a And |
Well Edit: + if anything, nix would not let you read files outside the flake because of the evaluation-time sandbox. |
I put my flake.nix under
/etc/nixos
, as this is where thesudo nixos-rebuild switch
default to. However, when I try to update the flake inputs bynh os switch --update
, it successfully pulls the updates, but failed to update the flake.lock file due to permission denied. I have to manually update the flake inputs before I run this command. I think nh should ask for sudo permission to update the lock, as/etc/nixos/flake.nix
is a common place that people will store their flake files.The text was updated successfully, but these errors were encountered: