From: zimoun <zimon.toutoune@gmail.com>
To: "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: bug#45069: Guix System: unprivileged user cannot create user namespaces?
Date: Mon, 07 Dec 2020 18:35:28 +0100 [thread overview]
Message-ID: <86ft4h5xjz.fsf@gmail.com> (raw)
In-Reply-To: <87tusxwncj.fsf@ambrevar.xyz>
Hi,
On Mon, 07 Dec 2020 at 18:13, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>> Can you try, as root on Guix System:
>>
>> $ echo 1 > /proc/sys/kernel/unprivileged_userns_clone
>
> # echo 1 > /proc/sys/kernel/unprivileged_userns_clone
> -bash: /proc/sys/kernel/unprivileged_userns_clone: No such file or directory
In gnu/build/linux-container.scm, it reads:
--8<---------------cut here---------------start------------->8---
(define (unprivileged-user-namespace-supported?)
"Return #t if user namespaces can be created by unprivileged users."
(let ((userns-file "/proc/sys/kernel/unprivileged_userns_clone"))
(if (file-exists? userns-file)
(eqv? #\1 (call-with-input-file userns-file read-char))
#t)))
--8<---------------cut here---------------end--------------->8---
Does it mean that the Linux kernel on Guix System does not support
namespaces by unprivileged users?
Turning #t to #f should work on Guix System and it appears to me a
severe bug if not. What do I miss? Please could someone fill my gap? :-)
All the best,
simon
next prev parent reply other threads:[~2020-12-07 17:45 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 ` zimoun [this message]
2020-12-07 17:55 ` bug#45069: Guix System: unprivileged user cannot create user namespaces? Vagrant Cascadian
2020-12-07 20:03 ` zimoun
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=86ft4h5xjz.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 \
/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.