If you give me a valid use case for USER_NS, I might reconsider, but
every use case I can imagine is crushed by the limitations of the
implementation.
The use case is that you don't need root access to start a container.
I can run Firefox with a limited view to the filesystem for
yey
thanks for CONFIG_USER_NS=y
On 4 August 2014 09:38, Tobias Powalowski
tobias.powalow...@googlemail.com wrote:
Hi,
just released 3.16 kernel to [testing] repository.
Only r8168 binary module did not build. Please take a look at it.
greetings
tpowa
--
Tobias Powalowski
Archlinux
On 13 August 2014 17:26, Damjan Georgievski gdam...@gmail.com wrote:
yey
thanks for CONFIG_USER_NS=y
ahh no, I'm stupid.
Checked it on another machine and got excited before hand
:/
anyway. is there a reason this is not enabled now?
all the mainstream distros hae it enabled now Fedora,
Am 13.08.2014 um 17:29 schrieb Damjan Georgievski:
On 13 August 2014 17:26, Damjan Georgievski gdam...@gmail.com wrote:
yey
thanks for CONFIG_USER_NS=y
ahh no, I'm stupid.
Checked it on another machine and got excited before hand
:/
anyway. is there a reason this is not enabled now?
Hi,
On Wed, Aug 13, 2014 at 06:44:39PM +0200, Thomas Bächler wrote:
Am 13.08.2014 um 17:29 schrieb Damjan Georgievski:
On 13 August 2014 17:26, Damjan Georgievski gdam...@gmail.com wrote:
yey
thanks for CONFIG_USER_NS=y
ahh no, I'm stupid.
Checked it on another machine and got
On 08/13/2014 08:09 PM, Leonid Isaev wrote:
As you know, user_ns is a necesary prerequisite for unpriviileged containers:
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ . AFAIU,
currently only Ubuntu 14.04 supports those.
However, I agree with you that CONFIG_USER_NS is
anyway. is there a reason this is not enabled now?
all the mainstream distros hae it enabled now Fedora, RHEL/CentOS 7,
Ubuntu and Debian (at least on the backported kernel)
I'd think about it, if the feature wasn't entirely useless. Despite the
lack of official documentation, I found a
On Wed, Aug 13, 2014 at 08:21:32PM +0300, Mihamina Rakotomandimby wrote:
Easing the work by defaulting to a ready-to-work kernel would be nice.
I think that LXC is used by minority of users (myself included). So, enabling
USER_NS by default would put the rest of (unsuspecting) users in
Am 13.08.2014 um 19:40 schrieb Damjan Georgievski:
anyway. is there a reason this is not enabled now?
all the mainstream distros hae it enabled now Fedora, RHEL/CentOS 7,
Ubuntu and Debian (at least on the backported kernel)
I'd think about it, if the feature wasn't entirely useless. Despite
On 13/08/14 12:44 PM, Thomas Bächler wrote:
Am 13.08.2014 um 17:29 schrieb Damjan Georgievski:
On 13 August 2014 17:26, Damjan Georgievski gdam...@gmail.com wrote:
yey
thanks for CONFIG_USER_NS=y
ahh no, I'm stupid.
Checked it on another machine and got excited before hand
:/
anyway. is
On 13/08/14 01:40 PM, Damjan Georgievski wrote:
anyway. is there a reason this is not enabled now?
all the mainstream distros hae it enabled now Fedora, RHEL/CentOS 7,
Ubuntu and Debian (at least on the backported kernel)
I'd think about it, if the feature wasn't entirely useless. Despite the
On 13/08/14 01:21 PM, Mihamina Rakotomandimby wrote:
On 08/13/2014 08:09 PM, Leonid Isaev wrote:
As you know, user_ns is a necesary prerequisite for unpriviileged
containers:
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
. AFAIU,
currently only Ubuntu 14.04 supports
12 matches
Mail list logo