I am proxmox 9.0.11 / 6.14.11-4-pve kernel.
When I create a LXC container the cgroups (v2) is actaully working inside the lxc guest. Except there is one annoyance:
cat /sys/fs/cgroup/memory.max always returns 'max', while other info does work. I.e. /sys/fs/cgroup/memory.current gives the current amount of RAM used in the LXC container.
Some .net software I run actually use this /sys/fs/cgroup/memory.max to know how many RAM can be used. In this case the software crashes after a while as I do set a memory limit, but this isn't respected by the .net software.
I found this as well:
When I create a LXC container the cgroups (v2) is actaully working inside the lxc guest. Except there is one annoyance:
cat /sys/fs/cgroup/memory.max always returns 'max', while other info does work. I.e. /sys/fs/cgroup/memory.current gives the current amount of RAM used in the LXC container.
Some .net software I run actually use this /sys/fs/cgroup/memory.max to know how many RAM can be used. In this case the software crashes after a while as I do set a memory limit, but this isn't respected by the .net software.
I found this as well:
We have a few LXCs (Proxmox 7.2-11) that have memory restrictions set using the normal method available in the Proxmox console. Generally things work great but there is one application we run in the containers that keep consuming memory until the container hits the limit and the OOM killer tries to free some.
We figured out that the application is overestimating the available memory by using the total host memory instead of the container memory. The host has 768GB and the containers have 2GB, so it is a big difference. Inside the containers some utilities (free &...
We figured out that the application is overestimating the available memory by using the total host memory instead of the container memory. The host has 768GB and the containers have 2GB, so it is a big difference. Inside the containers some utilities (free &...
- angus.dickey
- Replies: 5
- Forum: Proxmox VE: Installation and configuration