From: Jesse Gibbons <jgibbons2357@gmail.com>
To: help-guix@gnu.org
Subject: foreign guix offload checklist?
Date: Sun, 13 Dec 2020 21:39:48 -0700 [thread overview]
Message-ID: <8058bde5-f8fb-a3c6-97db-22f07605d869@gmail.com> (raw)
Hi guix,
I'm trying to offload a build onto a machine with a foreign distro. I'm
getting the following error:
$ guix build --system=armhf-linux --no-substitutes hello
The following derivations will be built:
/gnu/store/jidb0saw2s3zd1gvnziw064hbb1hxz7y-hello-2.10.drv
/gnu/store/hknqainda0ardh1ch1grrazislmmm1js-module-import-compiled.drv
/gnu/store/w9lgwyp9a9v12x0bja3brhqj5ilb6l93-hello-2.10.tar.gz.drv
process 22691 acquired build slot '/var/guix/offload/192.168.1.28:22/0'
normalized load on machine '192.168.1.28' is 0.02
building
/gnu/store/w9lgwyp9a9v12x0bja3brhqj5ilb6l93-hello-2.10.tar.gz.drv...
waiting for locks or build slots...
guix offload: error: failed to connect to `#<input-output: channel
(open) 7f5b4a378460>': Protocol error
cannot build derivation
`/gnu/store/jidb0saw2s3zd1gvnziw064hbb1hxz7y-hello-2.10.drv': 1
dependencies couldn't be built
guix build: error: build of
`/gnu/store/jidb0saw2s3zd1gvnziw064hbb1hxz7y-hello-2.10.drv' failed
Is there a checklist for what must be done to set up a machine with a
foreign distro as a build machine ("build slave")? Here's what I have so
far:
- [X] Make sure guile-ssh is installed on master. This should already be
done if master runs guix distro.
- [X] Configure slave to accept master's ssh key '~/.ssh/id_rsa.pub`. If
user wants to use configurations as close to default as possible, also
configure it to accept '/root/.ssh/id_rsa.pub'.
- [X] install guix on master
- [X] Exchange guix public keys between master and slave. If master runs
guix distro, the slave key should be added to the config.
- [X] Add slave to /etc/guix/machines.scm as described in the manual.
Am I missing any step?
reply other threads:[~2020-12-14 4:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8058bde5-f8fb-a3c6-97db-22f07605d869@gmail.com \
--to=jgibbons2357@gmail.com \
--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).