Quoting S.Çağlar Onur (cag...@10ur.org):
> OK I think I'm seeing something but haven't found the real problem,
> yet. Looks like some caller (or the caller of the caller etc.) is not
> checking the return code of the chown_mapped_root (from
> src/lxc/conf.c) function and trying to progress. That se
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: 6e39e4cbff5d49b4a66451696aa87b9884f58a6e
https://github.com/lxc/lxc/commit/6e39e4cbff5d49b4a66451696aa87b9884f58a6e
Author: Stéphane Graber
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M config/temp
Quoting Stéphane Graber (stgra...@ubuntu.com):
> This updates the common config to include Serge's seccomp profile by
> default for privileged containers.
>
> Signed-off-by: Stéphane Graber
Acked-by: Serge E. Hallyn
> ---
> config/templates/Makefile.am | 4 ++--
> config/templates/c
OK I think I'm seeing something but haven't found the real problem,
yet. Looks like some caller (or the caller of the caller etc.) is not
checking the return code of the chown_mapped_root (from
src/lxc/conf.c) function and trying to progress. That seems to be
causing this problem. The following pat
This updates the common config to include Serge's seccomp profile by
default for privileged containers.
Signed-off-by: Stéphane Graber
---
config/templates/Makefile.am | 4 ++--
config/templates/common.conf.in| 4
config/templates/common.seccomp| 8
config
Hey everyone,
Just wanted to send one more reminder about the upcoming LXC hackfest
happening on Friday August 22nd during LinuxCon North America.
A bunch of us will be present the rest of the week too, attending some
of the talks or just doing hallway hacking.
For those interested, we also sub
Hi,
I've started testing lxc 1.0.4 on our environment with ubuntu trusty images
and found an issue with the exit code of lxc-start.
On lxc 0.9.0 the exit code matches the container:
vagrant@vagrant-ubuntu-trusty-64:~$ sudo lxc-start -l debug -o lxc.log -n
u1 -- bash -c 'echo TEST && sleep 10 &&
Hey Stéphane,
On Mon, Jun 30, 2014 at 10:20 PM, Stéphane Graber wrote:
> On Mon, Jun 30, 2014 at 10:09:49PM -0400, S.Çağlar Onur wrote:
>> Hey there,
>>
>> This change set caused my go test suite to fail unexpectedly. Some of
>> my tests produced errors like
>>
>> === RUN TestClone
>> lxc_contain
