Replies: 3 comments 2 replies
-
I was just getting ready to add a couple LXC agents. I'll let you know if I have the same issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Probably, I'll look into it when I have time. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I know this is old, but I just set this up on Unraid, and I'm seenig the same issue. LXC shows the same (w/in about 0.2%) for memory and cpu as the host. But Unraid reports a more accurate 'very low' usage for the container as it's not doing much of anything right now. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When I setup the beszel-agent in my LXC running on Proxmox, the CPU and RAM that are shown reflect the host, rather than the Linux container running on it. I figure that's what LXC is reporting back, but wondering if there is a way to get the CPU and RAM to reflect the cores/ram/usage for the container, rather than the host running the container. Disk space does report just what the container has allocated.
In the below screenshot, proxmox is running on the host, and docker is the name of an LXC container running on the host.
Beta Was this translation helpful? Give feedback.
All reactions