Skip to content

馃悶 Bug: System resources overview is wrong聽#2416

Closed

Description

@Manriel

Bug Description

Resources overview in the dashboard page is wrong if arcane/agent deployed inside LXC container.

Steps To Reproduce

  1. Create unprivileged LXC container with nesting feature enabled.
  2. Limit container CPU/RAM resources
  3. Bind-mount some additional external storage to the container not in the root (/) but somewhere else.
  4. Make sure, that CPU binding inside LXC container have gaps/not in order (In my case it has CPU1 and CPU7 assigned, probably you'll have to recreate LXC several times in a row to achieve this)

Expected Behavior

It shows current CPU/RAM resources respecting LXC cgroups limits.
Disk usage show values based on system drive (with the / mountpoint).

Actual Behavior

It shows total host system memory value instead limited by cgroup.
It shows total CPU cores based on highest bound CPU number from the host, ignoring actual cgroup limits and core binding.
It shows disk usage of bind-mount instead of local root fs.

Screenshots

It currently show this:
Image
When actual resources it have are 2 CPUs, 2GB of RAM and 10Gb of storage in the root fs.

By the way, at the same time, this window shows the correct one info
Image

Arcane Version

v1.17.4

Installation Method

Docker Compose (Recommended)

Environment Type

Both Local and Remote Agents

Database Type

SQLite (Default)

Operating System

Linux

Docker Version

29.1.3, build f52814d454173982e6692dd7e290a41b828d9cbc

Browser & Version

Not related with browser

Relevant Logs or Error Messages

Haven't found related strings in logs

Docker Compose Configuration

services:
  arcane-agent:
    image: ghcr.io/getarcaneapp/arcane-headless:latest
    container_name: arcane-agent
    restart: unless-stopped
    environment:
      - AGENT_MODE=true
      - EDGE_TRANSPORT=poll
      - AGENT_TOKEN=###redacted###
      - MANAGER_API_URL=###redacted###
    ports:
      - "3553:3553"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
      - /proc:/proc
      - ./data:/app/data

Environment Configuration (.env file)

- empty -

Additional Context

No additional context needed

Activity

  1. added theissue type on Apr 22, 2026
  2. kmendell commented on Apr 23, 2026

    @kmendell
    Member

    should be fixed in the next version .

  3. Manriel commented on Apr 23, 2026

    @Manriel
    Author

    @kmendell, It does not.

    Image

    Still the same issue happened in 1.18.1

  4. theoraim commented on Jul 1, 2026

    @theoraim

    Hello, having the same issue here : LXC Container with 2CPUs, 4GB. Version is 2.3.0

    Image

    The details windows display the correct info :

    Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions