Bug Description
Updated to version 1.9 and added the /dev/dri device to my compose.yaml for Arcane. After bringing the container down and up again, the GPU is not showing on the dashboard. I went into the terminal for Arcane and can navigate to /dev/dri and see the devices. This might be tied to running Arcane on a virtualized Ubuntu server via Proxmox, so the GPU I want to monitor (Intel Arc A380) is not the primary GPU for the VM. In /dev/dri I see both card0 and card1, where card0 is the default GPU assigned to the VM automatically.
Steps To Reproduce
Updated Arcane to 1.9.
Added /dev/dri device to compose.yaml.
Possibly tied to being a VM and multiple "cards", when using a dedicated GPU for passthrough but not as the primary GPU for the VM. Used for hardware transcoding.
Expected Behavior
See the GPU resources on the dashboard.
Actual Behavior
No GPU charts showing on dashboard.
Screenshots
No response
Arcane Version
1.9
Operating System
Linux
Browser
Firefox, latest version
Docker Version
28.5.2
Additional Context
No response
Bug Description
Updated to version 1.9 and added the /dev/dri device to my compose.yaml for Arcane. After bringing the container down and up again, the GPU is not showing on the dashboard. I went into the terminal for Arcane and can navigate to /dev/dri and see the devices. This might be tied to running Arcane on a virtualized Ubuntu server via Proxmox, so the GPU I want to monitor (Intel Arc A380) is not the primary GPU for the VM. In /dev/dri I see both card0 and card1, where card0 is the default GPU assigned to the VM automatically.
Steps To Reproduce
Updated Arcane to 1.9.
Added /dev/dri device to compose.yaml.
Possibly tied to being a VM and multiple "cards", when using a dedicated GPU for passthrough but not as the primary GPU for the VM. Used for hardware transcoding.
Expected Behavior
See the GPU resources on the dashboard.
Actual Behavior
No GPU charts showing on dashboard.
Screenshots
No response
Arcane Version
1.9
Operating System
Linux
Browser
Firefox, latest version
Docker Version
28.5.2
Additional Context
No response