From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: “guix pack -RR r“ fails?
Date: Fri, 13 Nov 2020 00:21:01 +0100 [thread overview]
Message-ID: <865z6af9gi.fsf@gmail.com> (raw)
In-Reply-To: <87eekygvfm.fsf@gnu.org>
Hi,
On Thu, 12 Nov 2020 at 21:41, Ludovic Courtès <ludo@gnu.org> wrote:
>> Hum? I do not know if I am doing correctly. The packages
>> fakechroot-2.9-24.5.el6_1.1.x86_64.rpm and
>> fakechroot-libs-2.9-24.5.el6_1.1.x86_64.rpm are installed. And I get
>> as regular user:
>
> You do not need these packages: the tarball includes a copy of
> libfakechroot.so (see
> <https://hpc.guix.info/blog/2020/05/faster-relocatable-packs-with-fakechroot/>).
>
>> $ export GUIX_EXECUTION_ENGINE=fakechroot
>> $ strace -f -s 500 -o logg ./bin/R
>> fakechroot: unsupported Guix execution engine; ignoring
>
> You would need to use ‘guix pack -RR’ instead of ‘guix pack -R’ to get
> the ‘fakechroot’ execution engine.
>
>> However, as root, simply running ./bin/R returns:
>>
>> # ./bin/R
>> R: run.c:245: disallow_setgroups: Unexpected error: No such file or directory.
>> Abandon
>
> That indicates that user namespaces are not supported.
I have used ’-RR’ but because it is not working, then I tried to install
extra stuff in case. But if the kernel is not supporting the namespace,
that’s a end. Period.
> But wait, if you’re root, you can just as well upgrade to a kernel that
> supports unprivileged user namespaces… or even install Guix? :-)
That’s not so simple. It is an old RHEL and I am not sure that the
upgrading path is smooth… So I am applying the well-known rule: do not
fix it if it is not broken. ;-) Well, I do not want to spend hours to
figure out what is wrong with the new configuration (hardware).
Installing Guix (the package manager) cannot work because the same
problem: kernel.
I am configuring another machine (Dell T620) to smooth the switch. But
I hit the very same problem: spending hours to figure out what’s wrong
because I am missing obscure hardware configurations.
Thank you for your help.
Cheers,
simon
prev parent reply other threads:[~2020-11-12 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 18:13 “guix pack -RR r“ fails? zimoun
2020-11-05 12:38 ` Roel Janssen
2020-11-06 18:52 ` zimoun
2020-11-06 10:05 ` Ludovic Courtès
2020-11-06 18:48 ` zimoun
2020-11-08 17:34 ` Ludovic Courtès
2020-11-09 12:01 ` zimoun
2020-11-12 20:41 ` Ludovic Courtès
2020-11-12 23:21 ` zimoun [this message]
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=865z6af9gi.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.
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).