From: "U.Mutlu" <for-gmane@mutluit.com>
To: util-linux@vger.kernel.org
Subject: Re: unshare -m for non-root user
Date: Mon, 16 Nov 2015 03:01:54 +0100 [thread overview]
Message-ID: <n2bdei$vhf$1@ger.gmane.org> (raw)
In-Reply-To: <5648EA26.2080804@zoho.com>
Ángel González wrote on 11/15/2015 09:25 PM:
>>> complain to Debian. iirc, they break their kernels on purpose by adding
>>> non-standard caps which disallow userns usage.
>>
>> Ok, I found out that on Debian one needs to make the follwing entry in
>> /etc/sysctl.conf:
>> kernel.unprivileged_userns_clone = 1
>> and reboot, or do sysctl -p /etc/sysctl.conf, or equivalently
>> echo 1 > /proc/sys/kernel/unprivileged_userns_clone
>
> The kernel will neded to be compiled with CONFIG_USER_NS
True, but the stock Debian 8 kernel has it already enabled,
as the following tool (belongs to lxc) reports:
#######
$ lxc-checkconfig
Kernel configuration not found at /proc/config.gz; searching...
Kernel configuration found at /boot/config-3.16.0-4-amd64
--- Namespaces ---
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Network namespace: enabled
Multiple /dev/pts instances: enabled
--- Control groups ---
Cgroup: enabled
Cgroup clone_children flag: enabled
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: enabled
--- Misc ---
Veth pair device: enabled
Macvlan: enabled
Vlan: enabled
File capabilities: enabled
Note : Before booting a new kernel, you can check its configuration
usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
#######
Another method to see it is this one:
$ grep CONFIG_USER_NS /boot/config-`uname -r`
CONFIG_USER_NS=y
next prev parent reply other threads:[~2015-11-16 2:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 2:09 unshare -m for non-root user U.Mutlu
2015-10-30 10:22 ` Karel Zak
2015-11-14 2:43 ` U.Mutlu
2015-11-14 3:53 ` Eric W. Biederman
2015-11-14 7:25 ` U.Mutlu
2015-11-14 18:17 ` Isaac Dunham
2015-11-14 21:07 ` U.Mutlu
2015-11-15 0:49 ` U.Mutlu
2015-11-15 1:24 ` Mike Frysinger
2015-11-15 2:10 ` U.Mutlu
2015-11-15 6:28 ` Mike Frysinger
2015-11-15 12:06 ` U.Mutlu
2015-11-15 12:42 ` Mike Frysinger
2015-11-15 15:56 ` U.Mutlu
2015-11-15 18:49 ` Mike Frysinger
2015-11-15 20:25 ` Ángel González
2015-11-16 2:01 ` U.Mutlu [this message]
2015-10-30 16:49 ` Mike Frysinger
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='n2bdei$vhf$1@ger.gmane.org' \
--to=for-gmane@mutluit.com \
--cc=util-linux@vger.kernel.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.
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.