lxc-start fails on clone(child_stack=0, flags=CLONE_NEWNS|0x6c000000|SIGCHLD) = -1 EINVAL (Invalid argument)

Miguel F Mascarenhas Sousa Filipe miguel.filipe at gmail.com
Fri Jun 5 07:09:06 PDT 2009


On Fri, Jun 5, 2009 at 2:59 PM, Serge E. Hallyn<serue at us.ibm.com> wrote:
> Quoting Miguel F Mascarenhas Sousa Filipe (miguel.filipe at gmail.com):
>> Hello,
>>
>> I'm trying to play with lxc, but I'm unable to start a container
>> created with lxc-debian in two diferent linux systems I have.
>>
>> linux-2.6.29-gentoo-r5 x86_64.
>> linux-2.6.28-11-generic ubuntu x86_64.
>
> I suspect the problem is that your kernel (especially the ubuntu
> one) is compiled without CONFIG_NET_NS=y.
>
>> clone(child_stack=0, flags=CLONE_NEWNS|0x6c000000|SIGCHLD) = -1 EINVAL
>
> You are sending clone the flags LCON_NEWNS, CLONE_NEWNET, CLONE_NEWPID,
> CLONE_NEWUTS and CLONE_NEWIPC.  Of those, CLONE_NEWNET is the newest
> one.
>
> Are you free to recompile your kernel?

On my devel/test boxes yes, but I would like to use containers on
servers where I'm not going to have that "freedom".

I probably have to enable this:

User namespace: disabled
Network namespace: disabled
Multiple /dev/pts instances: disabled

Right?


thanks,

>
> thanks,
> -serge
>



-- 
Miguel Sousa Filipe


More information about the Containers mailing list