+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Help with Hardware Acceleration (/t-help-with-hardware-acceleration)
Help with Hardware Acceleration - foxhoundxgenome - 2023-06-21
I have finally got everything to work both locally and remotely, so now I would like to enable hardware acceleration, but am having some trouble.
From the official Jellyfin documentation here (https://jellyfin.org/docs/general/administration/hardware-acceleration/intel/#configure-with-linux-virtualization), I have tried:
Code:
docker run -d \
--name=jellyfin \
--volume /path/to/config:/config \
--volume /path/to/cache:/cache \
--volume /path/to/media:/media \
--user 1000:1000 \
--group-add="122" \ # Change this to match your "render" host group id and remove this comment
--net=host \
--restart=unless-stopped \
--device /dev/dri/renderD128:/dev/dri/renderD128 \
jellyfin/jellyfin*I replaced the volumes and the render group ID accordingly, and removed the comment for the group-add line
However, after entering the above in a Stack within Portainer, I receive this error message:
Quote:Deployment error
failed to deploy a stack: Top-level object must be a mapping
These are my specs:
Running Jellyfin in a Docker container via Portainer
OS: Ubuntu Server
GPU: Intel CoffeeLake-S GT2 [UHD Graphics 630]
Does anyone know what I'm doing wrong?
I have also tried the following solutions with no success:
https://www.youtube.com/watch?v=_RfH65swYNo
https://www.youtube.com/watch?v=VHXefJ7Ne6I
RE: Help with Hardware Acceleration - zackoid - 2023-06-22
I don't know what you're doing wrong because I don't use portainer, and I believe your issue is not specifying the container in the format they expect.
However you don't need to do it in portainer, you can run that on the command line. The only thing that is obviously wrong is you have placeholders instead of paths for your config, cache and media volumes. 1000:1000 and 122 are also not necessarily correct (or incorrect), those depend on the IDs of the user you want the container to run as, and of the group that owns the /dev/dri/rednderD128 device.