C Anthony Risinger writes:
> On Nov 29, 2010, at 12:17 AM, "Trent W. Buck"
> wrote:
>
>> Upstream cgroup documentation uses /dev/cgroup. I would appreciate a
>> udev rules.d file that creates and mounts a cgroup there; I haven't
>> gotten around to writing one
>
> docs lagging; upstream does th
On Nov 29, 2010, at 12:17 AM, "Trent W. Buck"
wrote:
> Upstream cgroup documentation uses /dev/cgroup. I would appreciate a
> udev rules.d file that creates and mounts a cgroup there; I haven't
> gotten around to writing one
docs lagging; upstream does this for us now:
/sys/fs/cgroup
http://
Siju George writes:
> 1) how do I limit the RAM usage of a container?
In lxc.conf(5):
lxc.cgroup.memory.limit_in_bytes = 256M
lxc.cgroup.memory.memsw.limit_in_bytes = 1G
> 2) how do I limit the disk usage of a container ?
Ensure the rootfs is a dedicated filesystem (e.g. an LVM LV), a
Alessandro Guido
writes:
> Whenever I shutdown a container /var/lib/lxc get remounted ro.
This is because the reboot/halt jobs in /etc/rc[06].d/ try to mount the
root filesystem read-only before halting, and you do not disallow this
in your /etc/lxc/.conf:
lxc.cap.drop = sys_admin
Note tha
"Brian K. White" writes:
> On 11/8/2010 1:14 PM, Michael H. Warfield wrote:
>> On Mon, 2010-11-01 at 08:40 -0500, Serge E. Hallyn wrote:
>>> Quoting Walter Stanish (walter.stan...@saffrondigital.com):
http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commitdiff_plain;h=c01d62f21b21ba
I encountered, isolated, and worked around this issue.
Symptom: gettys don't start in the container. runlevel(8) reports
"unknown" instead of "N 2".
Problem: ifupdown 0.6.8ubuntu29.1 introduces this change:
ifupdown (0.6.8ubuntu29.1) lucid-proposed; urgency=low
* debian/ifupdown.netw
