Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Tdarr error #293

Closed Answered by havardthom
travwide asked this question in Q&A
Nov 17, 2024 · 3 comments · 1 reply
Discussion options

I'm getting the following error when trying to deply tdarr.
/dev/dri/renderD128 is not a device
|
[ERROR] in line 657: exit code 0: while executing command pct start "$CTID"

WHen trying to start the LXC in Proxmox I receive this error.
TASK ERROR: /dev/dri/renderD128 is not a device

 ______ __ 
 /_ __/___/ /___ __________
 / / / __ / __ `/ ___/ ___/
 / / / /_/ / /_/ / / / / 
/_/ \__,_/\__,_/_/ /_/ 
 
Using Default Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 1
Using Root Password: Automatic Login
Using Container ID: 114
Using Hostname: tdarr
Using Disk Size: 4GB
Allocated Cores 2
Allocated Ram 2048
Using Bridge: vmbr0
Using Static IP Address: dhcp
Using Gateway IP Address: Default
Using Apt-Cacher IP Address: Default
Disable IPv6: No
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server Address: Host
Using MAC Address: Default
Using VLAN Tag: Default
Enable Root SSH Access: No
Enable Verbose Mode: No
Creating a Tdarr LXC using the above default settings
 ✓ Using containers for Template Storage.
 ✓ Using containers for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 114 was successfully created.
 \/dev/dri/renderD128 is not a device
 |
[ERROR] in line 657: exit code 0: while executing command pct start "$CTID"
You must be logged in to vote

Tdarr sets up hardware acceleration, perhaps a permission issue with /dev/dri/renderD128. What is the output of ls -l /dev/dri on your host?

Replies: 3 comments 1 reply

Comment options

Thats Not a Script issue, thats an issue with your Proxmox

You must be logged in to vote
0 replies
Comment options

Tdarr sets up hardware acceleration, perhaps a permission issue with /dev/dri/renderD128. What is the output of ls -l /dev/dri on your host?

You must be logged in to vote
1 reply
Comment options

root@pve:~# ls -l /dev/dri
total 0
drwxr-xr-x 2 root root 60 Nov 19 17:27 by-path
crw-rw---- 1 root video 226, 0 Nov 19 17:27 card0
---------- 1 root root 0 Nov 19 17:33 renderD128

Answer selected by travwide
Comment options

Looks like my pemission were off. I had to do the following,.

rm /dev/dri/renderD128
mknod /dev/dri/renderD128 c 226 128
chown root:video /dev/dri/renderD128
chmod 660 /dev/dri/renderD128

Verify the correct permissions and rerun the script.

root@pve:~# ls -l /dev/dri
total 0
drwxr-xr-x 2 root root 60 Nov 19 17:27 by-path
crw-rw---- 1 root video 226, 0 Nov 19 17:27 card0
crw-rw---- 1 root video 226, 128 Nov 20 17:04 renderD128

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
not a script issue This is not a script issue

AltStyle によって変換されたページ (->オリジナル) /