unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Sébastien Lerique" <sl@eauchat.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-science@gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: Re: Introducing Guix to HPC at my institution
Date: Thu, 01 Apr 2021 23:34:12 +0900	[thread overview]
Message-ID: <87k0pmysyk.fsf@eauchat.org> (raw)
In-Reply-To: <87mtui1jxn.fsf@gnu.org>

Hello!

On 01 Apr 2021 at 17:35, Ludovic Courtès 
<ludovic.courtes@inria.fr> wrote:

>> Case 1: with substitutes, on a local (non-NFS) folder
>> -----------------------------------------------------
>> [snip]
>
> Can you run guix-daemon like so?
>
>   LC_ALL=en_US.utf8 guix-daemon --disable-chroot &

Then:

  $ guix install hello --no-offload
  [... dowloading ...]
  13.3 MB will be downloaded
  substitution of 
  /gnu/store/395pvii4bcjqxvdv7h0drq10lxi01sv1-glibc-utf8-locales-2.31 
  failed
  guix install: error: some substitutes for the outputs of 
  derivation 
  `/gnu/store/b2jkmg71m0dpf3i6hvskb32ra48lls28-glibc-utf8-locales-2.31.drv' 
  failed (usually happens due to networking issues); try 
  `--fallback' to build derivation from source

Restarting from scratch and using `--fallback` then leads to the 
bzip2-mesboot failure of Case 2.

If, instead of resarting from scratch, I just run again `guix 
install hello --no-offload`, I then get:

  guix install: error: got unexpected path 
  `/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash: 
  warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)' 
  from substituter

And indeed once again lib/locale is a dead symlink, as the 
glibc-utf8-locales packaged in my tar.gz has been removed from the 
store. Why is that? I had a look through the same commands with 
--debug=4 or 5, but to no insight (aside from seeing locale 
derivations being deleted at some stage). I posted the end of the 
log produced by `guix install hello --no-offload --debug=4`, 
starting with the failed substitution, here: 
https://paste.debian.net/1191991/ .

> The “unexpected substitute message” thing is a bug: it turns out 
> that
> stderr of ‘guix substitute’ is consumed directly by the daemon 
> at this
> point, which it shouldn’t (similar to the issue fixed by
> ee3226e9d54891c7e696912245e4904435be191c).

Ok, I'll file a bug for that then :)

>> Case 2: from source (no substitutes), on a local (non-NFS) 
>> folder
>> -----------------------------------------------------------------
>> [snip]
>
> The problem is that ‘--disable-chroot’ is a bit of the wild 
> west: build
> processes can access the whole file system and what you do as a 
> user can
> interfere with them.
>
> It could be that the bzip2 build failure above is just that: the 
> build
> process picks something from /usr/lib or /usr/bin, and that 
> breaks
> everything.
>
> I think ‘--disable-chroot’ is OK if you’re going to use 
> substitutes for
> almost everything.  Otherwise, it’s not good.  Your use case 
> calls for
> built-in support; that way, the daemon could take still 
> advantage of
> user namespaces to set up a chroot and all.

I see. By the way, starting guix-daemon without `--disable-chroot` 
(and without substitutes) leads to:

  guix build: error: cannot change ownership of 
  ‘/gnu/store/0dn61y4n8ig333b23hmc80hvlcy8gdli-guile-bootstrap-2.0.drv.chroot’: 
  Invalid argument

so --disable-chroot is indeed still necessary! I am interested in 
working on this built-in support once I get the substitutes case 
working (although I will probably come ask for guidance for that) 
:)

Thanks!
Sébastien


  reply	other threads:[~2021-04-01 14:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  3:12 Introducing Guix to HPC at my institution Sébastien Lerique
2021-03-15 13:47 ` zimoun
2021-03-16  1:54   ` Sébastien Lerique
2021-03-16  8:06     ` zimoun
2021-03-16  9:05     ` Ludovic Courtès
2021-03-18  2:26       ` Sébastien Lerique
2021-03-26  8:22         ` Sébastien Lerique
2021-03-29 12:03           ` Ludovic Courtès
2021-03-30  1:54             ` Sébastien Lerique
2021-03-30  7:21               ` Ludovic Courtès
2021-03-31  5:23                 ` Sébastien Lerique
2021-04-01  8:35                   ` Ludovic Courtès
2021-04-01 14:34                     ` Sébastien Lerique [this message]
2021-04-10 20:43                       ` Ludovic Courtès
2021-04-12  1:21                         ` Sébastien Lerique
2021-04-12 12:43                           ` Ludovic Courtès

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=87k0pmysyk.fsf@eauchat.org \
    --to=sl@eauchat.org \
    --cc=guix-science@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    --cc=zimon.toutoune@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.
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).