On Mon, Sep 20, 2010 at 4:29 AM, l...@jelmail.com wrote:
> Hi Daniel,
>
> I have tracked down this issue somewhat. It seems to be caused by shutting
> down a container (not by lxc-stop) and is caused by the rc.shutdown script
> present in Arch Linux.
>
> I don't know what specifically causes the p
On 09/20/2010 11:13 AM, l...@jelmail.com wrote:
>
>> As mentioned Serge, that maybe the cgroup device white list which
>> prevent you to do that.
>> You can check by temporarly comment out in /var/lib/lxc/mycontainer all
>> the lxc.cgroup.devices lines and then launch the container again. I
On Mon, 2010-09-20 at 05:29 -0400, l...@jelmail.com wrote:
> Hi Daniel,
> I have tracked down this issue somewhat. It seems to be caused by shutting
> down a container (not by lxc-stop) and is caused by the rc.shutdown script
> present in Arch Linux.
I've seen this problem too even when lxc-stop
Hi Daniel,
I have tracked down this issue somewhat. It seems to be caused by shutting
down a container (not by lxc-stop) and is caused by the rc.shutdown script
present in Arch Linux.
I don't know what specifically causes the problem because I haven't had
time to investigate but I do know that it
> As mentioned Serge, that maybe the cgroup device white list which
> prevent you to do that.
> You can check by temporarly comment out in /var/lib/lxc/mycontainer all
> the lxc.cgroup.devices lines and then launch the container again. If
> you are able to mount it, then you should add in t
