Memory usage inside LXC

[wn6]

Hi all,

Any of my LXC containers in proxmox4.4 shows different memory usage from inside of container and in web interface.

In web interface memory usage looks good.

Inside of container swap always shows as 2GB capacity. Memory usage can be more than available (for example 282M/256M).

How can I get a correct info inside of container?

 

[LnxBil]

How can I get a correct info inside of container?

I think you have to wait until the problems are fixed upstream. General problem is that the container from the host perspective does need more memory than you have available inside. Do not forget the management overhead, it's less than with KVM, but it's there.

 

[BelCloud]

Are you using the latest official template for this OS from Proxmox? I had the same issue, but on migrated openvz containers.

 

[fabian]

Hi all,

Any of my LXC containers in proxmox4.4 shows different memory usage from inside of container and in web interface.

In web interface memory usage looks good.
View attachment 4540
Inside of container swap always shows as 2GB capacity. Memory usage can be more than available (for example 282M/256M).
View attachment 4541
How can I get a correct info inside of container?

is 2GB the swap size of the host? if so, this should be fixed with the next version ( 2.0.5-pve2) of our lxcfs package (see https://git.proxmox.com/?p=lxcfs.git;a=commit;h=3b716f2b274b2d2ae26c09e6ae17aaf81b016601 )

 

[LnxBil]

Sometimes it's also the implementation on the client, such that it'll report false values. Please refer to this discussion https://forum.proxmox.com/threads/alpine-lxc-container.30169/

 

[wn6]

Thank you for your replies.
BelCloud, I'm using proxmox4.4 from a template in soyoustart.com (OVH). You are right, the issue is related to migrated openvz containers.
fabian, yes, 2GB is the swap size of the host. Thank you.
LnxBil, thank you, really 'free' shows correct info instead of 'htop'.

 

[LnxBil]

LnxBil, thank you, really 'free' shows correct info instead of 'htop'.

That is also implementation specific. /proc/meminfo should hold the entries reported by the LXC abstraction, so that is the "real" source.