From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: yasu <yasu@yasuaki.com>
Cc: 45069@debbugs.gnu.org, zimon.toutoune@gmail.com,
pgarlick@tourbillion-technology.com, guix-devel@gnu.org,
pjotr.public12@thebird.nl
Subject: bug#45069: BUG: Re: guix environment: error: cannot create container: unprivileged user cannot create user namespaces
Date: Sun, 06 Dec 2020 17:16:41 +0100 [thread overview]
Message-ID: <87k0tux63a.fsf@nckx> (raw)
In-Reply-To: <bde9689feb5e69e4e3dcb027be33fe1ca30a7227.camel@yasuaki.com>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
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.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-06 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e5c86d238ca5174b745b8ea6cb0cb6ad6b20aa5e.camel@yasuaki.com>
[not found] ` <CAJ3okZ19V7jh8SEOSKR+kMw_9qCWupjiHecNi+0v2A_fKH2EKQ@mail.gmail.com>
[not found] ` <20201204185537.qhapfbyaq7cr5lkr@thebird.nl>
[not found] ` <4556420c9440a6c34df93213e3934176e214483f.camel@yasuaki.com>
2020-12-06 12:41 ` BUG: Re: guix environment: error: cannot create container: unprivileged user cannot create user namespaces yasu
2020-12-06 16:16 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-12-06 16:56 ` zimoun
2020-12-06 20:51 ` yasu
2021-01-06 10:49 ` raingloom
[not found] ` <CADdvwM-h6q9BvO5ZWxgUbHfdzDRc-Sj899ZPgrwqV5o1XUVnDg@mail.gmail.com>
2020-12-07 11:57 ` bug#45069: " Pierre Neidhardt
[not found] ` <1f56aef4d7b707826f34413672408e33385bbc6a.camel@tourbillion-technology.com>
2020-12-07 12:41 ` Yasuaki Kudo
[not found] ` <87tusxwncj.fsf@ambrevar.xyz>
2020-12-07 19:50 ` Paul Garlick
[not found] ` <87im9dwe07.fsf@ambrevar.xyz>
2020-12-07 21:09 ` zimoun
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
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=87k0tux63a.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=45069@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
--cc=pgarlick@tourbillion-technology.com \
--cc=pjotr.public12@thebird.nl \
--cc=yasu@yasuaki.com \
--cc=zimon.toutoune@gmail.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 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).