Fernando Ayats
Fernando Ayats
Some info: `boot.isContainer` adds the `container@` service template, which can read entries in `/etc/nixos-container/name.conf`
No idea what the issue could be. Have you tried to run `sudo /tmp/nh-os-iVxsvr/result/bin/switch-to-configuration test` on your regular terminal?
For any `os` command, it doesn't create any `/tmp/nh-os-*` folder? EDIT: Also, what is your nix version?
And if you run the nix build command manually? ``` mkdir -p /tmp/nh-os-iVxsvr nix build '/home/thom/.config/nixos#nixosConfigurations."nix-lat".config.system.build.toplevel' --out-link /tmp/nh-os-iVxsvr/result ```
The directory must be created by your user, and you should be able to do so from the permissions of `/tmp`: ``` $ stat --format="%a" /tmp 1777 ```
Then I have no idea why nix doesn't create the symlink if ran within nh
Ah right, I just remember I use the crate `tempfile` for the outlink, which is cleared after nh exits, with errors or not. > I have the impression, that nh...
Could you run with --verbose and paste the output?
And you have sudo?
> removing obsolete file ‘/etc/sudoers’... Please use ` nh os rebuild -R` if you plan to remove sudo.