YAMS Forum

Evening all!

I previously had all this YAMS setup running, but with multiple issues caused by having two hard drives. Since downgrading to a single hard drive, those particular issues have gone. However, as with all these things I now have another even WORSE issue!

Anything 4K will not playback on ANY device I try, just a black screen with a playback error message.

The system has a dedicated Nvidia GPU which was working FINE previously... I cant seem to work out as to why the GPU passthrough stuff just isnt working this time round? I didnt do a damn thing last time to make docker use the hardward onboard. Granted, to get an nvidia GPU to work on Debian is a whole pain in the arse anyway but still..

Its deeply frustrating as this is the 4th time ive tried YAMS and every time theres a stupid issue that I cant seem to figure out. I've previously just run jelly fin on my proxmox server and manually added films and had zero issues... so why the hell is this now happening?

Hey @tyredformat!

Have you confirmed that your graphics card is transcoding correctly? Check Jellyfin's docs here: https://docs.linuxserver.io/images/dock ... in/#nvidia

This has nothing to do with YAMS, you need to correctly pass trough your graphics card to your VM and then configure Jellyfin to use it.

Cheers!

Roger.

Unfortunately ive tried all the above and all I get is errors, it wont even try to play.

Worst of all is now my docker-compose.yaml is having a fit so I cant even use the yams restart command

yaml: unmarshal errors:
  line 3: cannot unmarshal !!seq into cli.named
Waiting for services to startyaml: unmarshal errors:
  line 3: cannot unmarshal !!seq into cli.named

compose yaml as follows:

services:
  # jellyfin is used to serve your media to the client devices
  jellyfin:
    image: lscr.io/linuxserver/jellyfin
    container_name: jellyfin
    #network_mode: host # plex
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - e NVIDIA_VISIBLE_DEVICES=all
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${MEDIA_DIRECTORY}:/data
      - ${INSTALL_DIRECTORY}/config/${MEDIA_SERVICE}:/config
    ports: # plex
      - 8096:8096 # plex
    restart: unless-stopped

And the error logs from Jellyfin pretty much agree with my thoughts, for reasons only it knows its not using HW Acceloration at all. Despite the fact its config'd exactly as before!!

ffmpeg version 7.1.1-Jellyfin Copyright (c) 2000-2025 the FFmpeg developers
  built with gcc 13 (Ubuntu 13.3.0-6ubuntu2~24.04)
  configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto=auto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libharfbuzz --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
  libavutil      59. 39.100 / 59. 39.100
  libavcodec     61. 19.101 / 61. 19.101
  libavformat    61.  7.100 / 61.  7.100
  libavdevice    61.  3.100 / 61.  3.100
  libavfilter    10.  4.100 / 10.  4.100
  libswscale      8.  3.100 /  8.  3.100
  libswresample   5.  3.100 /  5.  3.100
  libpostproc    58.  3.100 / 58.  3.100
[b][AVHWDeviceContext @ 0x55e563833840] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x55e563833840] Could not dynamically load CUDA
Device creation failed: -1.
Failed to set value 'cuda=cu:0' for option 'init_hw_device': Operation not permitted
Error parsing global options: Operation not permitted[/b]

To fix your docker-compose.yml file, you can verify it here: https://jsonformatter.org/yaml-formatter

Regarding the GPU pass-trough, that greatly depends on your OS configuration and hardware. This has nothing to do with YAMS. I know there's people on the Discord that have solved this before, so I suggest you join the discord and ask around!

Cheers!

Roger.

BTW, I found the error:

This is not valid YAML. - e NVIDIA_VISIBLE_DEVICES=all is completely wrong

rogs wrote: ↑Tue Jun 24, 2025 6:45 pm

BTW, I found the error:

This is not valid YAML. - e NVIDIA_VISIBLE_DEVICES=all is completely wrong

Hi again! This actually doesnt cause the error. I tried verifying the YAML using the site you sent (when I googled youd suggested that for someone else too lol) and it says its valid.

Even removing that line gives me the same error with line 3. Again, not a clue why....

Hmmm, weird... Either way, the correct one should be

      - NVIDIA_VISIBLE_DEVICES=all

(the -e is only if you are using plain docker, but YAMS uses docker-compose).

I have no idea why the other problem is happening to be honest, this is the first time I see that...