Closed happysalada closed 1 year ago
@happysalada Can you do the following:
nix-info -m
I should start versioning Nixinate, and it is something I intend to do, there's also a few things the VM Tests fail to catch as noted in #32, I'm working on a big update that uses recursive-nix and impure-derivations to perform deployments in the Nix sandbox, so watch this space.
My suspicion is that I expect this issue to have something to do with the host-architecture you're deploying from, as the only change I've made recently is to make hermetic builds the default, which means a quick fix would be to set hermetic to false
explicitly in your Nixinate arguments, if this is the case.
that was indeed what broke it. I have no idea what hermetic is, but you can't do it on a remote build apparently. Thanks for the quick response!
@happysalada Hermetic is documented in the README. What it will do is copy nix
and nixos-rebuild
to the remote machine, rather than impurely executing the nixos-rebuild on the remote machine, assuming it is there.
oh that makes sense, I'm on a darwin machine and trying to build on a linux machine. That's why it doesn't work. Ok, thanks for the explanation!
Yeah, it's why I didn't make hermetic default for the longest time, but I figure the most common use case is probably going to be aided by hermetic. I reckon there's a way of making the remote realise its own Nix instead of even having to evaluate the drv on the local machine, making it truly hermetic, without having this flaw of being unable to realise the drv for a foreign architecture.
hey I've just updated to the latest nixinate master and it seems to be giving me the following error
Do I need to change anything ?