From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Roman Inflianskas <infroma@gmail.com>, help-guix@gnu.org
Subject: Re: Guix + User Namespaces wrapper (UGuix)
Date: Wed, 24 Feb 2021 15:21:54 +0100 [thread overview]
Message-ID: <8735xlczr1.fsf@elephly.net> (raw)
In-Reply-To: <877dnl9r3i.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> If I recall correctly, some contributors were discussing this feature
> some time ago on the mailing list. (Was it with Ludo?)
It should already be possible to use “guix pack guix” (with a few extra
options) to generate a relocatable Guix with a daemon that can run as an
oblivious root inside the execution container.
The only missing bits then are to let the Guix command line tool talk to
the wrapped daemon, but perhaps that also works by setting the daemon
socket environment variable.
--
Ricardo
prev parent reply other threads:[~2021-02-24 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 14:25 Guix + User Namespaces wrapper (UGuix) Roman Inflianskas
2021-02-06 15:02 ` Pierre Neidhardt
2021-02-24 14:21 ` Ricardo Wurmus [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=8735xlczr1.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=infroma@gmail.com \
--cc=mail@ambrevar.xyz \
/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).