-
Notifications
You must be signed in to change notification settings - Fork 416
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
SSH connection with linux-builder fails #913
Comments
I've been working on something similar. One thing I did find, which may help you, is that if you are going to overwrite "config" it might be necessary to also enable SSH. In other words, add Secondly, it doesn't seem like logging is enabled by default. I had to add the following to my top level config: Hope some of this helps. |
I'm able to successfully build with the linux-builder however unable to personally ssh in. What is the password is it asking for? |
@georgealexanderday it would help to see full output as well as your invocation. Even better if you add some debugging to the invocation with For what it's worth, I'm able to SSH directly to the builder VM from a fresh setup. |
If you are looking to ssh into the image I have managed to do that by using the private key generated when the machine image is created; e.g. edit
In this case the private key has been placed in /etc/nix/builder_ed25519 by nix-darwin. However I am having the same issue as workingdodge where I can ssh into the image but I can not seem to get ssh-ng to work when using the machine image as a builder. |
Actually after further investigation I managed to get it to work I had updated the permissions to 644 on the |
I can confirm a similar behavior:
|
I'm able to ssh into linux-builder when I manually pass the ssh key and config, so the instance is running.
Failing with error:
connecting to 'ssh-ng://builder@linux-builder'... cannot build on 'ssh-ng://builder@linux-builder': error: failed to start SSH connection to 'builder@linux-builder'
Not quite sure how to introspect the ssh session when calling
nix build
The text was updated successfully, but these errors were encountered: