unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 39366@debbugs.gnu.org
Subject: bug#39366: guix offload sometimes can use ~/.ssh/config, sometimes not
Date: Wed, 05 Feb 2020 12:11:09 +0100	[thread overview]
Message-ID: <87sgjpp9v6.fsf@gnu.org> (raw)
In-Reply-To: <87blqkrueq.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 31 Jan 2020 01:50:53 -0500")

Hi,


Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> "hurd" is a host name defined in my ~/.ssh/config file.
>
> $ guix offload status
> guix offload: getting status of 1 build machines defined in '/etc/guix/machines.scm'...

[...]

> $ guix offload test
> guix offload: testing 1 build machines defined in '/etc/guix/machines.scm'...
> guix offload: Guix is usable on 'hurd' (test returned "/gnu/store/883yjkl46dxw9mzykykmbs0yzwyxm17z-test")

[...]

> $ guix build git --no-substitutes --check
> process 31348 acquired build slot '/var/guix/offload/hurd:22/0'
> guix offload: error: failed to connect to 'hurd': Failed to resolve hostname hurd (Name or service not known)

That is confusing indeed.  It comes from the fact that ‘guix offload’ in
the last case is running as root; thus, it sees a different
~/.ssh/config.

We could instruct ‘guix offload’ to always ignore ~/.ssh/config, but
that wouldn’t be great because using it can be useful.

Perhaps it should emit a warning when not running as root?

Thanks,
Ludo’.

  reply	other threads:[~2020-02-05 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31  6:50 bug#39366: guix offload sometimes can use ~/.ssh/config, sometimes not Maxim Cournoyer
2020-02-05 11:11 ` Ludovic Courtès [this message]
2021-12-16 13:39   ` zimoun
2022-01-03 16:58     ` Ludovic Courtès
2022-01-03 17:24       ` zimoun

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=87sgjpp9v6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39366@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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 public inbox

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

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).