Hi there.
I remember reading in another thread in this forum that. this was not an Proxmox issue but some kind of bugs between lxcfs and cgroups2 or something like that but I am now unable to find the thread. For me, as all my containers are monitored from custom agents inside the container for load and memory this simply blocks my upgrade path, and I will be in pve6 until this gets addressed (if gets addressed).
The alternative for me is develop/deploy a new monitoring system running on the physical Proxmox hosts for more than 200 containers, which is currently not an option.
@Dunuin if you are using zabbix agent inside the container (I am also for some of my nodes), I have just created my own items for reading memory. The right memory values inside the container can be found in /proc/meminfo so you just create an item which reads this, using
key = vfs.file.contents[/proc/meminfo]
and then just create dependent items which parse the values of the original item to generate the free/used/avalable/total items.
I remember reading in another thread in this forum that. this was not an Proxmox issue but some kind of bugs between lxcfs and cgroups2 or something like that but I am now unable to find the thread. For me, as all my containers are monitored from custom agents inside the container for load and memory this simply blocks my upgrade path, and I will be in pve6 until this gets addressed (if gets addressed).
The alternative for me is develop/deploy a new monitoring system running on the physical Proxmox hosts for more than 200 containers, which is currently not an option.
@Dunuin if you are using zabbix agent inside the container (I am also for some of my nodes), I have just created my own items for reading memory. The right memory values inside the container can be found in /proc/meminfo so you just create an item which reads this, using
key = vfs.file.contents[/proc/meminfo]
and then just create dependent items which parse the values of the original item to generate the free/used/avalable/total items.
