Am 25.03.2014 20:30, schrieb Serge Hallyn:
> Quoting Florian Klink (flo...@flokli.de):
>> Hi,
>>
>> I have the problem that filesystems mounted with lxc.hook.pre-mount stay
>> mounted the whole time, even after the container is stopped.
>>
>> According to my understandinding, mountpoints mounted by
Quoting Florian Klink (flo...@flokli.de):
> Hi,
>
> I have the problem that filesystems mounted with lxc.hook.pre-mount stay
> mounted the whole time, even after the container is stopped.
>
> According to my understandinding, mountpoints mounted by these hook
> scripts will be private to the cont
Hi,
I have the problem that filesystems mounted with lxc.hook.pre-mount stay
mounted the whole time, even after the container is stopped.
According to my understandinding, mountpoints mounted by these hook
scripts will be private to the container and cleaned up on container
stop automatically (ma
Thanks for all the replies.
On Tue, Mar 25, 2014 at 12:22 AM, Flo wrote:
> Hi,
>
> max_usage is the amount of memory that WAS used by the container at it's
> maximum(!) since it was started.
>
> Regards,
> Flo
>
>
> On Mon, Mar 24, 2014 at 1:34 PM, Mingjiang Shi wrote:
>
>> Thank you, Andreas.
Dear David,
In short: Currently not, but there is work in progress.
Greetings
Guido
>-Original Message-
>From: lxc-users-boun...@lists.linuxcontainers.org
>[mailto:lxc-users-boun...@lists.linuxcontainers.org] On Behalf Of David
>Shwatrz
>Sent: Tuesday, March 25, 2014 1:42 PM
>To: LXC
Hi,
I hade added a limit of 512 M and using only CPU #0 in an LXC container
config file:
lxc.cgroup.memory.limit_in_bytes = 512M
lxc.cgroup.cpuset.cpus = 0
Now, from within the container, cat /proc/meminfo and cat
/proc/cpuinfo, as well as free(), will
show infromation about the host, not about t
