SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-21 21:42:07 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Debian 13 VAAPI-enabled LXCs need a different GID for passthrough #1945

New Issue
Closed
opened 2025-11-20 05:20:27 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:20:27 -05:00
Owner
Copy Link

Originally created by @vhsdream on GitHub (Sep 24, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Immich

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

New LXCs that use Debian 13 and require VAAPI device passthrough (/dev/dri/renderD128) are still using GID 104 as the render group, but in Trixie the GID has changed to 992.

🔄 Steps to reproduce the issue.

Install Immich from scratch and choose to enable all VAAPI devices.

❌ Paste the full error output (if available).

In the 'Resources' tab for a new Immich LXC:
Image

Within the Immich LXC:
Image

root@immich-new:~# ls -l /dev/dri
total 0
crw-rw---- 1 root video    226,   0 Sep 24 12:17 card0
crw-rw---- 1 root postdrop 226, 128 Sep 24 12:17 renderD128

🖼️ Additional context (optional).

I think the solution will require support for both Debian 12 and 13 since I don't think all LXCs that have the VAAPI option are using Debian 13 yet.

Originally created by @vhsdream on GitHub (Sep 24, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Immich ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. New LXCs that use Debian 13 and require VAAPI device passthrough (`/dev/dri/renderD128`) are still using GID 104 as the `render` group, but in Trixie the GID has changed to 992. ### 🔄 Steps to reproduce the issue. Install Immich from scratch and choose to enable all VAAPI devices. ### ❌ Paste the full error output (if available). In the 'Resources' tab for a new Immich LXC: <img width="613" height="252" alt="Image" src="https://github.com/user-attachments/assets/3afd8ae3-a669-43a2-8079-398d500559c3" /> Within the Immich LXC: <img width="199" height="63" alt="Image" src="https://github.com/user-attachments/assets/1bef6d8a-404e-4dd2-bc6f-a0bba8916c34" /> ``` root@immich-new:~# ls -l /dev/dri total 0 crw-rw---- 1 root video 226, 0 Sep 24 12:17 card0 crw-rw---- 1 root postdrop 226, 128 Sep 24 12:17 renderD128 ``` ### 🖼️ Additional context (optional). I think the solution will require support for both Debian 12 and 13 since I don't think all LXCs that have the VAAPI option are using Debian 13 yet.
saavagebueno added the bug label 2025-11-20 05:20:27 -05:00
saavagebueno commented 2025-11-20 05:20:28 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 24, 2025):

Its currently not relevant. Core in VED Push it Automatic to the given uid/gid. The big bang come in next 2-3 weeks

@MickLesk commented on GitHub (Sep 24, 2025): Its currently not relevant. Core in VED Push it Automatic to the given uid/gid. The big bang come in next 2-3 weeks
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1945
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?