On 2019-06-18 11:59, Stéphane Graber wrote:
So we have plans to introduce project quotas which will allow placing
such restrictions in a clean way through LXD.
Until then you can manually tweak /sys/fs/cgroup/memory/lxc or
/sys/fs/cgroup/memory/lxc.payload (depending on version of liblxc) as
On Tue, Jun 18, 2019 at 09:47:19AM +0900, Tomasz Chmielewski wrote:
> Let's say I have a host with 32 GB RAM.
>
> To make sure the host is not affected by any weird memory consumption
> patterns, I've set the following in the container:
>
> limits.memory: 29GB
>
> This works quite well -
On 2019-06-18 11:34, Fajar A. Nugraha wrote:
You could probably just use nested lxd instead:
https://stgraber.org/2016/12/07/running-snaps-in-lxd-containers/
Set the outer container memory limit to 29GB, and put other containers
inside that one.
Yeah, but that's a bit "hackish" (to achieve
On Tue, Jun 18, 2019 at 7:47 AM Tomasz Chmielewski wrote:
> Let's say I have a host with 32 GB RAM.
>
> To make sure the host is not affected by any weird memory consumption
> patterns, I've set the following in the container:
>
>limits.memory: 29GB
>
> This works quite well - where
Let's say I have a host with 32 GB RAM.
To make sure the host is not affected by any weird memory consumption
patterns, I've set the following in the container:
limits.memory: 29GB
This works quite well - where previously, several processes with high
memory usage, forking rapidly (a
Sorry, I don't understand why it doesn't work... Same config is
successful with my buster host.
Did you try it on a fresh buster install? Did you tweak things around?
Xavier
Le 17/06/2019 à 18:47, Lukas Pirl a écrit :
Ping… no ideas on this?
Forwarded Message
From: Lukas
Ping… no ideas on this?
Forwarded Message
From: Lukas Pirl
To: lxc-users@lists.linuxcontainers.org
Subject: Re: [lxc-users] unprivileged Debian Buster container on Debian Buster
host fail to start: no cgroups, no controllers
Date: Wed, 29 May 2019 00:11:29 +0200
> On Tue,
