unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesse Dowell <jesse.dowell@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>,
	45069@debbugs.gnu.org, pgarlick@tourbillion-technology.com
Subject: Re: bug#45069: BUG: Re: guix environment: error: cannot create container: unprivileged user cannot create user namespaces
Date: Sun, 6 Dec 2020 15:54:52 -0500	[thread overview]
Message-ID: <CADdvwM-h6q9BvO5ZWxgUbHfdzDRc-Sj899ZPgrwqV5o1XUVnDg@mail.gmail.com> (raw)
In-Reply-To: <86eek2an53.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

Hi All,

I believe the recommended suggestion is Debian specific is it not?

My kernel supports user namespaces and doesn't expose that file at that
location.

The only way I can work around the issue is to downgrade guix to the commit
on the master branch right before 8bc5ca5160db3d82bd5b6b2b7ed80c96f42bd33e

guix pull --commit=0d5d1bdf911659f60601058e8e1678187b7ba664
--allow-downgrades

Best,
Jesse

On Sun, Dec 6, 2020 at 12:03 PM zimoun <zimon.toutoune@gmail.com> wrote:

> Hi,
>
> Please try the recommendation. Have you tried it?
>
>   please set /proc/sys/kernel/unprivileged_userns_clone to "1"
>
> As root, you just do:
>
>   echo 1 > /proc/sys/kernel/unprivileged_userns_clone
>
> then “guix environment -C” should work as expected.  To do the trick
> automatically with Sheperd, I do not know, but I am sure that the
> systemd equivalent
>
>   echo "kernel.unprivileged_userns_clone = 1" > /etc/sysctl.d/local.conf
>   sysctl --system
>
> seems doable with Guix System.
>
>
> On my system, and I need explanations if it does not work similarly on
> yours, I simply do:
>
> --8<---------------cut here---------------start------------->8---
> $ guix environment -C --ad-hoc hello -- hello
> 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"
>
> $ su -
> Password:
> # echo 1 > /proc/sys/kernel/unprivileged_userns_clone
> # logout
>
> $ guix environment -C --ad-hoc hello -- hello
> Hello, world!
> --8<---------------cut here---------------end--------------->8---
>
> Hope that helps,
> simon
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2284 bytes --]

  parent reply	other threads:[~2020-12-06 20:55 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           ` Jesse Dowell [this message]
2020-12-07 11:57             ` bug#45069: " 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
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

  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=CADdvwM-h6q9BvO5ZWxgUbHfdzDRc-Sj899ZPgrwqV5o1XUVnDg@mail.gmail.com \
    --to=jesse.dowell@gmail.com \
    --cc=45069@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=pgarlick@tourbillion-technology.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).