Jellyfin Media Server LXC cannot start container #1198

Closed
opened 2026-02-04 23:34:13 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @brainhig on GitHub (Jun 30, 2025).

Have you read and understood the above guidelines?

Yes

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

Jellyfin Media Server

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📝 Provide a clear and concise description of the issue.

Creating Jellyfin container in Proxmox, using latest public release, community edition, script fails on starting container with error:

Starting LXC Container/dev/dri/renderD128 is not a device

I am not using GPU passthrough.

I see there was another issue previously with the same error, but no resolution was reported.

🔄 Steps to reproduce the issue.

In Proxmox shell, issue command:

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

Container is created, but cannot start. Screenshot included.

Image

Image

Paste the full error output (if available).

Starting LXC Container/dev/dri/renderD128 is not a device

🖼️ Additional context (optional).

No response

Originally created by @brainhig on GitHub (Jun 30, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Jellyfin Media Server ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 📝 Provide a clear and concise description of the issue. Creating Jellyfin container in Proxmox, using latest public release, community edition, script fails on starting container with error: Starting LXC Container/dev/dri/renderD128 is not a device I am not using GPU passthrough. I see there was another issue previously with the same error, but no resolution was reported. ### 🔄 Steps to reproduce the issue. In Proxmox shell, issue command: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)" Container is created, but cannot start. Screenshot included. ![Image](https://github.com/user-attachments/assets/1218cd76-0460-482a-b0b5-fd7e9703d0d9) ![Image](https://github.com/user-attachments/assets/bcdc7b86-0e0a-474c-aab1-d43832be0e41) ### ❌ Paste the full error output (if available). Starting LXC Container/dev/dri/renderD128 is not a device ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue label 2026-02-04 23:34:13 +03:00
Author
Owner

@MickLesk commented on GitHub (Jun 30, 2025):

Whats your GPU?

@MickLesk commented on GitHub (Jun 30, 2025): Whats your GPU?
Author
Owner

@brainhig commented on GitHub (Jul 1, 2025):

As far as I know, it is a Matrox G200. The built-in graphics card for a Dell R420 server. Definitely cannot be used for hardware decoding.

@brainhig commented on GitHub (Jul 1, 2025): As far as I know, it is a Matrox G200. The built-in graphics card for a Dell R420 server. Definitely cannot be used for hardware decoding.
Author
Owner

@MickLesk commented on GitHub (Jul 1, 2025):

Try Advanced with Privileged Container.

@MickLesk commented on GitHub (Jul 1, 2025): Try Advanced with Privileged Container.
Author
Owner

@brainhig commented on GitHub (Jul 3, 2025):

Thank you, that worked just fine!

@brainhig commented on GitHub (Jul 3, 2025): Thank you, that worked just fine!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1198