From: Kitty-Cricket Piapiac <kitty@piapiac.org>
To: help-guix@gnu.org
Subject: guix deploy: Failed to read private key
Date: Tue, 14 Feb 2023 00:59:11 -0800 [thread overview]
Message-ID: <e2800d28-62d2-d25e-2fce-451bdc1783f0@piapiac.org> (raw)
Hello Guix,
I am relatively new to this package manager & system distribution. I am
really struggling to get `guix deploy` working. I have a simple
`deploy.scm` that looks something like this.
$ cat deploy.scm
(define %os (operating-system ...))
(define %ip "<ip>")
(define %key "<host-key>")
(list
(machine
(operating-system %os)
(environment managed-host-environment-type)
(configuration (machine-ssh-configuration
(host-name %ip)
(host-key %key)
(identity "id_ed25519")))))
When I try and run `guix deploy deploy.scm` as a regular user, I get the
following error:
$ guix deploy deploy.scm
The following 1 machine will be deployed:
<name>
guix deploy: deploying to <name>
guix deploy: error: failed to deploy <name>: SSH authentication
failed for '<ip>': Failed to read private key: /home/kitty/.ssh/id_ed25519
At first I thought there may be a permissions issue, but the private key
is there, and with seemingly the right permissions,
$ ll /home/kitty/.ssh/id_ed25519
-rw------- 1 kitty users 464 Feb 13 00:03 id_ed25519
and ssh-ing into the machine normally works fine,
$ ssh root@<ip>
Enter passphrase for key '/home/kitty/.ssh/id_ed25519':
Last login: Mon Feb 13 17:24:54
root@<name> ~#
so I'm not really sure what could be causing this, and I'm not sure what
to do now to troubleshoot. Anybody run into this before, or any ideas?
Thanks,
Kitty-Cricket Piapiac
next reply other threads:[~2023-02-14 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 8:59 Kitty-Cricket Piapiac [this message]
2023-02-14 12:47 ` guix deploy: Failed to read private key Efraim Flashner
2023-02-15 3:07 ` Kitty-Cricket Piapiac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2800d28-62d2-d25e-2fce-451bdc1783f0@piapiac.org \
--to=kitty@piapiac.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).