From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>, 62253@debbugs.gnu.org
Subject: bug#62253: Fakechroot execution engine doesn’t outlive ‘exec’ calls
Date: Sat, 18 Mar 2023 22:47:52 +0100 [thread overview]
Message-ID: <87jzzd68af.fsf@jpoiret.xyz> (raw)
In-Reply-To: <877cveuvov.fsf@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
Hi Ludo,
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> I can think of several ways to address that:
>
> 1. Change the exec* wrappers in libfakechroot such that, on ENOENT,
> they try a direct ld.so invocation to run program, like
> ‘run-in-namespace.c’ does.
>
> Problem is that for this to work correctly, it would need to
> compute the ‘--library-path’ argument at run time, by computing the
> equivalent of (map dirname (file-needed/recursive program)).
> Impractical at best.
>
> 2. Wrap/graft every package in the closure (as opposed to generating
> wrappers for just those packages that appear in the profile, which
> is what ‘guix pack’ currently does).
>
> The downside is that the “userns” and “proot” execution engines
> don’t need something this heavyweight: they just need a leaf
> package to be wrapped.
>
> 3. Ignore the problem. After all, we’re talking about a corner case
> of the “fakechroot” engine, which is a niche within a niche.
>
> Food for thought…
I would like to be proven wrong, but I don't think anyone has run into
this, and there are other possible engines (that do require more
privileges, sure). It seems quite non-trivial to fix, so this can
probably go on the back-burner until someone actually complains (please
do so).
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-03-18 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 11:48 bug#62253: Fakechroot execution engine doesn’t outlive ‘exec’ calls Ludovic Courtès
2023-03-18 21:47 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-03-20 9:17 ` Ludovic Courtès
2023-04-18 12:09 ` 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=87jzzd68af.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=62253@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludovic.courtes@inria.fr \
/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).