Help: Proxmox update changed group id's

se7entynine

New Member
Dec 21, 2023
2
0
1
Hey,
I'm using the latest proxmox version and noticed that my /dev/dri/renderD128 device ( Intel iGPU ) has the wrong group "crontab" instead of "render". The render gid was 108 before the update and now it's 104. Crontab took the 108 group id.
The privileged lxc that uses my igpu for transcoding can't find the proper device anymore probably because of the groups ( https://logpaste.com/515SqdQX - nearly at the bottom of the logs ).
I tried to change the device group with
/bin/chgrp render /dev/dri/renderD128, but everytime I restart my lxc it resets itself to the crontab group. Cronjob or rc.local weren't successful either.
Changing the group within the lxc doesn't solved my problem too, as seen with lxc.hook.pre-start: sh -c "chown 0:108 /dev/dri/renderD128" in the lxc.conf file or manually as ffmpeg still can't find the device.
I included my setup and differnet commands in this link: https://logpaste.com/vcpSw78E

Any idea what I can try to solve this?
 
Apparently changing the lxc.conf file from
YAML:
lxc.hook.pre-start: sh -c "chown 0:108 /dev/dri/renderD128"
to
YAML:
lxc.hook.pre-start: sh -c "chown 0:render /dev/dri/renderD128"
solved this issue. I don't know why as 108 is the "render" id in the lxc.

Is there a way to monitor what application or process makes changes to the device group?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!