I, again, am thinking about combining Silverblue as my base system with a more complex Nix setup to replace toolbox (which is effectively a separate whole Linux to maintain or throw away regularly, or build a CI for to create new images, etc. -- nah).
Now, Nix works fine, but it needs to store things under /nix because most binaries are prefix dependent and not portable in their location. But what if I download the nix store to $HOME/.nix instead and then launch a light-weight throw-away container/namespace that simply maps $HOME/.nix to /nix but keeps everything else identical?
Would that work? Did someone already build that stuff?
@ljrk is there an issue with using the “/nix” path? I’ve used Silverblue in the past and am currently on a “downstream” distro from that. The Nix installer from Determinate Systems “just works” on these ostree based distros. (Not sure how, exactly, but it does.)
@pauldoo Nothing critical, no. Some things don't vibe with that as much, such as the "portable home" idea from systemd-homed, as well as kinda needing to elevate privileges just to install something irks me. Also means that every user can effectively overwrite binaries other users use... possibly elevating privileges or at least going lateral.
It's nothing that's game breaking but something that I'd prefer to be different.
Add comment