GNU bug report logs - #45066
guix environment --container is borken

Previous Next

Package: guix;

Reported by: luhux <luhux <at> outlook.com>

Date: Sun, 6 Dec 2020 09:15:01 UTC

Severity: normal

Merged with 45069

Done: Marius Bakke <marius <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 45066-done <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Marius Bakke <marius <at> gnu.org>, luhux <luhux <at> outlook.com>,
 45066-done <at> debbugs.gnu.org
Subject: Re: bug#45066: guix environment --container is borken
Date: Mon, 07 Dec 2020 01:52:23 +0100
Hi Marius,

On Sun, 06 Dec 2020 at 22:02, Marius Bakke <marius <at> gnu.org> wrote:

>> Have you tried the recommendation?

> It was broken.  :-)

[...]

> ...because this only works on the Debian kernel.

Therefore, what does the recommendation mean?  From [1] on 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---


1: <https://yhetil.org/guix/e5c86d238ca5174b745b8ea6cb0cb6ad6b20aa5e.camel <at> yasuaki.com>


> We need to find a more robust test for user namespaces, but for now I
> reverted the commit.

How do you «set /proc/sys/kernel/unprivileged_userns_clone to "1"» on
Guix System?


BTW, reverting means reopen #31977; I did.


All the best,
simon





This bug report was last modified 4 years and 133 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.