-
Notifications
You must be signed in to change notification settings - Fork 42
nix-copy-closure
, nix copy
doesn't work
#149
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
Comments
Okay, I must have done something wrong with my fake ssh binary testing. It appears the problem was indeed ssh not being available in the bwrap context. After I put However, it still runs into problems with This means For some more context, the reason that I was making use of If anyone else tries to also use nix-portable with nixos-rebuild, note that the nixos-rebuild script does some things that make using nix-portable somewhat harder by default:
As a workaround, I made a copy of the nixos-rebuild script and commented out the line forcing |
nix-copy-closure
: unable to execute 'ssh'nix-copy-closure
, nix copy
doesn't work
With something like #150, we would be able to run |
Uh oh!
There was an error while loading. Please reload this page.
I've been trying to use nix-copy-closure to copy the build products, and very strangely an error is complaining that the
ssh
file doesn't exist. After some debugging, I've determined that most options don't matter, and using a minimal nix-portable nix-copy-closure command triggers the error:./nix-portable-aarch64 nix-copy-closure --to a@b
(Yes, ssh exists on my machine).
I'm running nix-portable-012, and this seems to occur whether I use NP_RUNTIME
nix
,bwrap
, orproot
.This is puzzling, as judging from the error message, the external program call comes from
src/libstore/ssh.cc
(or more unlikelily, fromsrc/nix/run.cc
) of the NixOS/nix repository, and they do useexecvpe()
which should get ssh from my PATH. I tried adding fake binaries in NP_LOCATION and corresponding PATH entries, and that didn't work either.The text was updated successfully, but these errors were encountered: