Feature Request: Monitoring lxc container begin Host server

[psicodelico6]

Hi! .. I suggest that Zabbix could check host server and use de command "lxc exec CONTAINER COMMAND" for get cpu load or memory or disk ... etc. The container dont need agent. The detection for new containers would automatic.

[kloczek]

Issue is that LXC developers should implement proper isolation of the CPU,, memory usage which normally exposed over procfs to not be forces to use any special templates and just use regular Linux one.
Current state of the is that even kernel buffer messages are not separated between zones and global zone as well (you see over zone kernel messages what happens on physical box).

In other words: compare to for example Solaris zones .. Linux LXC sucks and I don't think that it will change soon (IMO definitely as long as that project is under control of morons from IBM).
On Solaris for example whole network layer is done without bridges and if lets say in global zone you have something like net0 as physical network interface you will see in list of interfaces attached to that physical NIC net0/<zone_name> and under zone just net0 (in other words you will have 100% impression that you are working on physical box and not in the zone).

If you want to have proper HW utilisation for bunch of Linux small system I would recommend use OminiOS with lx zones (Linux branded zones running on top of Solaris kernel in which Linux binaries negatively are running as Solaris processes .. sometimes faster/better than on Linux) and as ado-on you will have ZFS underneath (doing massive zones deployment without for example at least brtfs is IMO horrible idea because lack of possibility sharing page caches across zones for processes started from exactly the same binaries).

On Solaris you can use regular Solaris template within zone and the same should be done without any additional tricks under Linux. My Solaris template for example generates only when it is used in global zone set of LLDs which adds set of metrics about state of the zone (configured/installed/running) to raise some alarm that suddenly state of some zone changed or zone has been added/deleted.

LXC is around from more than decade and still many basic functionalities are not finished. User space tooling is still crappy. For example On Solaris you have only two commands for whole zones management: and administration zoneadm and zoneffg.