This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies. For details on cookie usage on our site, read our Privacy Policy
Thanks for your comments.
Regardless of how the agent will run in the LXC container, the host server itself is experiencing the high CPU load. We'll open a ticket for that specifically.
Our security group is insisting on having the cortex agent installed on every server - unfortunately we have a number of servers running as containers. Since the LXC container processes are just isolated by namespace while sharing the host kernel, and the host sees all these processes anyhow, I agree that the agent probably shouldn't be running in an LXC container at all.
... View more
We use a cluster of Proxmox servers which host a number of LXC containers and KVM/QEMU VMs. Our central IT department requires use to install the Cortex XDR agent on all the devices. I have a Debian Bookworm server with the cortex agent installed which only consumes between 0.0-0.3% CPU. On the Proxmox servers, this CPU usage is about 140%. Making things worse, each LXC container shares the host's kernel and for every pmd process in hosted LXC containers these processes show up on the Proxmox server host as additional pmd processes also running at 140% CPU usage.
I see plenty of documentation about Docker/Kubernetes and VM templates, but none of it applies to Linix containers.
Any suggestions as to how to get this to behave?
... View more