From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: Re: “guix system container” script must run as root
Date: Tue, 09 Aug 2022 18:23:14 +0200 [thread overview]
Message-ID: <87tu6luz81.fsf@elephly.net> (raw)
In-Reply-To: <87y1vxv2q3.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Guix,
>
> I see that the container script generated by “guix system container”
> must be run as root. Looking at “initialize-user-namespace” in (gnu
> build linux-container) there is conditional code to be executed only
> when running as an unprivileged user, namely writing to
> /proc/pid/setgroups. This makes me think that this was originally meant
> to be usable without root privileges.
>
> Without root privileges write access to /proc/pid/* is denied. The
> child process here is the result of issuing a clone syscall.
>
> Why can’t the parent process write to the child’s /proc/pid/* files?
“man 7 user_namespaces” explains what conditions must be met for a
parent process to write to /proc/childpid/uid_map. There are many
conditions that could lead to EPERM. It seems that writing to
/proc/pid/setgroups succeeds and only writing to uid_map and gid_map
fails.
The parent process should be able to write to these files at least
once; as the parent it should have the capabilities CAP_SETUID and
CAP_SETGID in the child process namespace.
--
Ricardo
prev parent reply other threads:[~2022-08-09 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 15:13 “guix system container” script must run as root Ricardo Wurmus
2022-08-09 16:23 ` 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=87tu6luz81.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@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).