2024-06-19, 07:00 PM
(This post was last modified: 2024-06-19, 07:42 PM by pol77. Edited 4 times in total.)
OK guys... Major breakthrough and I'm very excited.
The positive:
I have resolved my composer issues - it was just formatting as I'm totally ignorant. I can now create the container fine.
I have managed to script a container and it worked with version 10.8.9 and I did hardware transcoding with my GPU!!!
The negative:
I still have one issue to resolve. The drive mapping for config and cache to my shared folders in the NAS seem to be read only and the container starts and stops... The only way I was able to get it to run as above was to remove the cache and config mappings and allow it to create the folders inside the container, which is not ideal as it makes it very annoying to backup and restore.
The ugly:
Obviously, after all the issues re resolved I will have to spend a couple of very tedious days to fix my metadata (again).
Here is my composer file:
If you guys can see why the created cache and config folders seem to be read only I would be obliged. My buess is that the mapping needs to be a bind, but I don't know the code for that. It worked as a bind when I was doing it through th eGUI.
Edit:
FOUND IT.
This is the code that worked.
The only thing that did not seem to work is that I was expecting to be able to access the UI at port 32666 but it seems I can access it at 8096, which is weird but I don't care. It is all working and it is thanks to your help!
A million thank yous and I hope other people will see this thread and get help if they are facing the same issue.
I have also opened a case with QNAP and asked them to update the nvidia drivers! We'll see how that goes.
The positive:
I have resolved my composer issues - it was just formatting as I'm totally ignorant. I can now create the container fine.
I have managed to script a container and it worked with version 10.8.9 and I did hardware transcoding with my GPU!!!
The negative:
I still have one issue to resolve. The drive mapping for config and cache to my shared folders in the NAS seem to be read only and the container starts and stops... The only way I was able to get it to run as above was to remove the cache and config mappings and allow it to create the folders inside the container, which is not ideal as it makes it very annoying to backup and restore.
The ugly:
Obviously, after all the issues re resolved I will have to spend a couple of very tedious days to fix my metadata (again).
Here is my composer file:
Code:
version: '3'
services:
jellyfin:
image: jellyfin/jellyfin:10.8.9
container_name: PolFlix
user: '1000:1000'
network_mode: host
environment:
- VERSION=docker
- LD_LIBRARY_PATH=/share/ZFS530_DATA/.qpkg/NVIDIA_GPU_DRV/usr:/usr/local/nvidia/lib
- NVIDIA_VISIBLE_DEVICES=all
- NVIDIA_DRIVER_CAPABILITIES=all
ports:
- '32666:8096'
- '32667:8920'
volumes:
- '/share/Container/jellyfin/config:/config'
- '/share/Container/jellyfin/cache:/cache'
- '/share/Storage/Movies:/Movies:ro'
- '/opt/NVIDIA_GPU_DRV/usr:/usr/local/nvidia:ro'
devices:
- '/dev/nvidia0:/dev/nvidia0'
- '/dev/nvidiactl:/dev/nvidiactl'
- '/dev/nvidia-uvm:/dev/nvidia-uvm'
restart: unless-stopped
If you guys can see why the created cache and config folders seem to be read only I would be obliged. My buess is that the mapping needs to be a bind, but I don't know the code for that. It worked as a bind when I was doing it through th eGUI.
Edit:
FOUND IT.
This is the code that worked.
Code:
version: '3'
services:
jellyfin:
image: jellyfin/jellyfin:10.8.9
container_name: PolFlix
user: '1000:1000'
network_mode: host
environment:
- VERSION=docker
- LD_LIBRARY_PATH=/share/ZFS530_DATA/.qpkg/NVIDIA_GPU_DRV/usr:/usr/local/nvidia/lib
- NVIDIA_VISIBLE_DEVICES=all
- NVIDIA_DRIVER_CAPABILITIES=all
ports:
- '32666:8096'
- '32667:8920'
volumes:
- type: bind
source: /share/Container/jellyfin/config
target: /config
- type: bind
source: /share/Container/jellyfin/cache
target: /cache
- '/share/Storage/Movies:/Movies:ro'
- '/opt/NVIDIA_GPU_DRV/usr:/usr/local/nvidia:ro'
devices:
- '/dev/nvidia0:/dev/nvidia0'
- '/dev/nvidiactl:/dev/nvidiactl'
- '/dev/nvidia-uvm:/dev/nvidia-uvm'
restart: unless-stopped
The only thing that did not seem to work is that I was expecting to be able to access the UI at port 32666 but it seems I can access it at 8096, which is weird but I don't care. It is all working and it is thanks to your help!
A million thank yous and I hope other people will see this thread and get help if they are facing the same issue.
I have also opened a case with QNAP and asked them to update the nvidia drivers! We'll see how that goes.