all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Lars-Dominik Braun <ldb@leibniz-psychology.org>
Cc: 39925@debbugs.gnu.org
Subject: bug#39925: `guix pull` failure in multi-machine setup
Date: Sun, 08 Mar 2020 12:40:33 +0100	[thread overview]
Message-ID: <87zhcraxce.fsf@gnu.org> (raw)
In-Reply-To: <20200306114548.GD2909@zpidnp36> (Lars-Dominik Braun's message of "Fri, 6 Mar 2020 12:45:48 +0100")

Hi,

Lars-Dominik Braun <ldb@leibniz-psychology.org> skribis:

>> Sounds like this ssh URI is not valid on the nodes, is that right?
> I would consider it valid, since `ssh master.<domain>` and `guix build
> <package>` both work just fine from the nodes. It’s just `guix pull`, which is
> causing issues.

Oh it may be that we would also need to let ‘HOME’ through, so that
~/.ssh/config is found, for example.  That could have undesirable side
effects that are best avoided, though (e.g., ~/.cache/guile would become
visible.)

>> Right.  So perhaps I don’t quite understand the use case.  What about
>> simply pulling from one of these machines, if everything is shared over
>> NFS?
> Sure, that’s an option, but anyone who tries will get a strange error message.

I agree that the error message is sub-optimal.  Not sure how to improve
on it (how can ‘build-self.scm’ know that it’s failing because of
that?).

> And it breaks the appeal of having a remote guix daemon in the first place,
> that is being able to run `guix <whatever>` on any machine I log into. If that
> is not the case (i.e. not for `guix pull`) it would be more consistent to ask
> users to SSH into a different machine every time they interact with guix. Does
> that explain my use case?

Instead of:

  GUIX_DAEMON_SOCKET=ssh://host guix pull

You could run:

  ssh host guix pull

In fact, the former would probably not work because ‘guix pull’ modifies
the local /var/guix/profiles, not the one on the host that runs the
daemon.

So maybe the problem is that ‘GUIX_DAEMON_SOCKET=ssh://’ isn’t quite as
powerful as you thought.  :-)  It’s really just a way to talk to a remote
daemon, but ‘guix pull’, ‘guix package’, etc. also need to access
/var/guix/profiles.

Thanks,
Ludo’.

  reply	other threads:[~2020-03-08 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 13:33 bug#39925: `guix pull` failure in multi-machine setup Lars-Dominik Braun
2020-03-05 17:20 ` Ludovic Courtès
2020-03-06  7:40   ` Lars-Dominik Braun
2020-03-06 10:53     ` Ludovic Courtès
2020-03-06 11:45       ` Lars-Dominik Braun
2020-03-08 11:40         ` Ludovic Courtès [this message]
2020-03-09  8:22           ` Lars-Dominik Braun
2020-03-09 10:46             ` Ludovic Courtès
2020-03-10  7:19               ` Lars-Dominik Braun

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhcraxce.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39925@debbugs.gnu.org \
    --cc=ldb@leibniz-psychology.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.