From: zimoun <zimon.toutoune@gmail.com>
To: "Vagrant Cascadian" <vagrant@debian.org>,
"Ludovic Courtès" <ludo@gnu.org>, "Marius Bakke" <marius@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>,
45069@debbugs.gnu.org,
Paul Garlick <pgarlick@tourbillion-technology.com>,
Jesse Dowell <jesse.dowell@gmail.com>
Subject: Re: bug#45069: Guix System: unprivileged user cannot create user namespaces?
Date: Mon, 07 Dec 2020 21:03:58 +0100 [thread overview]
Message-ID: <86360h5qoh.fsf@gmail.com> (raw)
In-Reply-To: <87eek1sdpo.fsf@yucca>
Hi Vagrant,
Sorry if I am naive, I am trying to understand and it appears that
pieces are missing in my bag. :-)
On Mon, 07 Dec 2020 at 09:55, Vagrant Cascadian <vagrant@debian.org> wrote:
> The /proc/sys/kernel_unprivileged_userns_clone file is specific to
> Debian and Ubuntu packaged linux kernel; it is a patchset not applied
> upstream, as far as I am aware. I'm not sure if other distros support
> disabling and enabling this feature using this mechanism.
Thanks. I still do not understand the message from Guix System:
--8<---------------cut here---------------start------------->8---
~/co/guix (master)$ guix environment -C guix
guix environment: error: cannot create container: unprivileged user cannot create user namespaces
guix environment: error: please set /proc/sys/kernel/unprivileged_userns_clone to "1"
--8<---------------cut here---------------end--------------->8---
(see
<https://yhetil.org/guix/e5c86d238ca5174b745b8ea6cb0cb6ad6b20aa5e.camel@yasuaki.com>)
Why does this appear if «set /proc/sys/kernel/unprivileged_userns_clone to "1"»
does not make sense on Guix System?
Then Tobias answered: (see <https://yhetil.org/guix/87k0tux63a.fsf@nckx>)
yasu 写道:
> Now, I don't use Debian at all (I use Guix System) and do you
> think
> this is a Bug in Guix (in that this Debian specific word should
> never
> even be mentioned in Guix?)
It's not Debian-specific. It is a bug in Guix.
It should try to create a namespace and properly report an error
iff that fails, not prematurely abort after farting about in
/proc.
A separate unprivileged-user-namespace-supported? is broken by
design. Reverting commit 8bc5ca5 works around this but it wasn't
to blame.
so I miss why does a similar patch as,
> https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/patches/debian/add-sysctl-to-disallow-unprivileged-CLONE_NEWUSER-by-default.patch
is not applied to Guix System? Is it because a technical or else reason
behind? Or is it simply because no one takes the time to fix the
problem?
All the best,
simon
next prev parent reply other threads:[~2020-12-07 20:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 15:52 guix environment: error: cannot create container: unprivileged user cannot create user namespaces yasu
2020-12-04 16:04 ` Ricardo Wurmus
2020-12-04 16:29 ` Yasuaki Kudo
2020-12-04 16:32 ` zimoun
2020-12-04 18:55 ` Pjotr Prins
2020-12-04 20:44 ` Yasuaki Kudo
2020-12-05 0:20 ` yasu
2020-12-06 12:41 ` BUG: " yasu
2020-12-06 16:16 ` bug#45069: " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-12-06 16:56 ` zimoun
2020-12-06 20:51 ` yasu
2021-01-06 10:49 ` raingloom
2020-12-06 20:54 ` bug#45069: " Jesse Dowell
2020-12-07 11:57 ` Pierre Neidhardt
2020-12-07 12:29 ` Paul Garlick
2020-12-07 12:41 ` Yasuaki Kudo
2020-12-07 17:13 ` Pierre Neidhardt
2020-12-07 17:35 ` bug#45069: Guix System: unprivileged user cannot create user namespaces? zimoun
2020-12-07 17:55 ` Vagrant Cascadian
2020-12-07 20:03 ` zimoun [this message]
2020-12-08 3:20 ` Bengt Richter
2020-12-07 19:50 ` bug#45069: BUG: Re: guix environment: error: cannot create container: unprivileged user cannot create user namespaces Paul Garlick
2020-12-07 20:35 ` Pierre Neidhardt
2020-12-07 21:09 ` zimoun
2021-01-04 9:11 ` Pierre Neidhardt
2020-12-07 13:26 ` zimoun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86360h5qoh.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=45069@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=jesse.dowell@gmail.com \
--cc=ludo@gnu.org \
--cc=marius@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
--cc=vagrant@debian.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.