Hi Gary
On Tue, 2011-08-16 at 06:38 +1200, Gary Ballantyne wrote:
Unfortunately, I am still getting the same errors with a little over 40
containers.
I also had this problem. It was solved after Daniel suggested me to
increase the following sysctl setting:
fs.inotify.max_user_instances
Hi,
I experienced the same problem, but could (partially) solve it by
disabling IPv6 forwarding on all container's interfaces with sysctl.
Kind regards,
Karl
--
uberSVN's rich system and user administration
On 08/12/2011 11:00 PM, sfrazt wrote:
Hi,
i want to to have a application container that acts with memory limits
as there is simple no more memory. Means: if it reaches the limit the
next question for more memory should simple be denied.
The default behaviour is to kill the application when
On 08/12/2011 11:51 PM, Papp Tamas wrote:
hi!
I'm asking you about limiting memory.
This is the test config:
lxc.cgroup.memory.limit_in_bytes = 16M
lxc.cgroup.memory.memsw.limit_in_bytes = 1G
lxc.cgroup.cpuset.cpus = 0-1
lxc.cgroup.cpu.shares = 1024
I run apt-get upgrade and an openfire
On 08/13/2011 01:54 PM, John wrote:
I've just replaced my lxc package with lxc-git and it's working
again. Many thanks.
(my installed lxc package was probably one version stale also, which
was most likely the problem)
I guess there's been a change in the kernel. before seeing your response
On 08/15/2011 10:05 PM, Gary Ballantyne wrote:
On 16/08/11 06:52, Andre Nathan wrote:
Hi Gary
On Tue, 2011-08-16 at 06:38 +1200, Gary Ballantyne wrote:
Unfortunately, I am still getting the same errors with a little over 40
containers.
I also had this problem. It was solved after Daniel
