Hi,
I created a basic archlinux container (using almost the template):
lxc-create -n test -t archlinux
I now start the container
lxc-start -n test
In another shell, I attach inside it:
lxc-attach -n test [/bin/bash]
And I see the root file system of the host!
However, when I get into the ma
You failed to enable user namespace (which is clearly stated in the log you
posted).
Try enabling the user namespace and retest.
--
Pozdraviam
Wojtek
On Tuesday, 25 February 2014 at 10:34, Florian Klink wrote:
> Hi,
>
> I created a basic archlinux container (using almost the template):
>
>
Hi Wojtek,
thanks for your answer!
I built a kernel with the same config, but with CONFIG_USER_NS set to "y".
lxc-checkconfig now also reports user namespace as "enabled".
But when I run lxc-attach, I still see the root file system of the host,
not of the container...
So the problem is not us
Hi Florian,
Could you please post your configs? What lxc version are you using
btw? Build from scratch or installed from sys packages?
On 25 February 2014 14:25, Florian Klink wrote:
> Hi Wojtek,
>
> thanks for your answer!
>
> I built a kernel with the same config, but with CONFIG_USER_NS set t
Hi Wojtek,
lxc is "community/lxc 1:1.0.0-2" from archlinux repository. (seems to be
the same as git@lxc-1.0.0, except some systemd unit files and cosmetic
documentation fixes).
Host system runs archlinux amd64, 3.13.5-zen kernel, all packages up to
date.
lxc-create -n test -t archlinux creates:
We both did some more investigation, and Wojtek also was able to
reproduce the issue on debian wheezy with lxc-1.0.0 build from source.
The problem seems to be that lxc-attach doesn't set any namespaces (or
doesn't set them correctly)
By peeking into /proc/{pid_of_process_started_by_lxc-attach}/n
Quoting Florian Klink (flo...@flokli.de):
>
>
>
> Hi Wojtek,
>
> thanks for your answer!
>
> I built a kernel with the same config, but with CONFIG_USER_NS set to "y".
>
> lxc-checkconfig now also reports user namespace as "enabled".
>
>
> But when I run lxc-attach, I still see the root fil
Am 25.02.2014 21:43, schrieb Serge Hallyn:
> Quoting Florian Klink (flo...@flokli.de):
>>
>>
>>
>> Hi Wojtek,
>>
>> thanks for your answer!
>>
>> I built a kernel with the same config, but with CONFIG_USER_NS set to "y".
>>
>> lxc-checkconfig now also reports user namespace as "enabled".
>>
>>
>> B
this happen with fedora as well,
i tested with lxc 1.0, (make rpm , with --prefix=/usr, --enable-python), on
fedora 20. for me if i ssh into the container, i can see the container
rootfs, but if i attach using lxc-attach -n /bin/bash , it shows the host
rootfs
regards
ranjib
On Tue, Feb 25, 2014
Am 25.02.2014 22:40, schrieb Florian Klink:
> Am 25.02.2014 21:43, schrieb Serge Hallyn:
>> Quoting Florian Klink (flo...@flokli.de):
>>>
>>>
>>>
>>> Hi Wojtek,
>>>
>>> thanks for your answer!
>>>
>>> I built a kernel with the same config, but with CONFIG_USER_NS set to "y".
>>>
>>> lxc-checkconfig
10 matches
Mail list logo