From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: lxc and subuid
Date: Fri, 01 Apr 2022 10:12:39 +0200 [thread overview]
Message-ID: <87pmm1p6h4.fsf@gnu.org> (raw)
In-Reply-To: <bdadd81f9b12c9ea50c4c38af4cb37d25825fc50.camel@telenet.be> (Maxime Devos's message of "Wed, 30 Mar 2022 13:30:22 +0200")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> Antonio Carlos Padoan Junior schreef op wo 30-03-2022 om 08:51 [+0200]:
>> Hello,
>>
>> I'm trying to figure out how to set a unprivileged container using lxc
>> in guix. I do not know either how to allocate subuid/gid space in guix,
>
> subuid/gid are _not_ unprivileged. They are an userspace feature by
> the (privileged) setuid binary 'newuidmap', see
> <https://manpages.debian.org/buster/uidmap/newuidmap.1.en.html>.
>
> I don't think there's currently a mechanism for that in Guix System,
> except manually creating and modifying /etc/subuid appropriately and
> installing the setuid binaries. However, I suppose that the 'user-
> account' record could be extended to support subuid/subgid and
> automatically create /etc/subuid.
Or we could unconditionally add 65536 subuids for each non-system user
account; that’s what other distros seem to be doing.
I think we could take advantage of it for ‘guix system container’: it
could run in an unprivileged user namespace and map several UIDs in that
namespace, such that it doesn’t need to run as root anymore.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-04-01 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8vwj5la.fsf.ref@yahoo.com.br>
2022-03-30 6:51 ` lxc and subuid Antonio Carlos Padoan Junior
2022-03-30 11:30 ` Maxime Devos
2022-03-30 13:13 ` Antonio Carlos Padoan Junior
2022-03-30 13:23 ` Maxime Devos
2022-04-01 8:12 ` Ludovic Courtès [this message]
2022-04-02 13:52 ` Maxime Devos
2022-04-03 13:50 ` Antonio Carlos Padoan Junior
2022-04-05 11:53 ` 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=87pmm1p6h4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).