Should I mount the GPU for a docker setup with vaapi.

trevor

I am using Docker Compose. Here is my file:

services:
    ersatztv:
      image: jasongdove/ersatztv:latest-vaapi
      restart: unless-stopped
      volumes:
          - './media:/media:ro'
          - './config:/root/.local/share/ersatztv'
      tmpfs:
          - '/root/.local/share/etv-transcode'
      ports:
          - '8409:8409'
      environment:
          - TZ=America/New_York
      container_name: ersatztv

For VAAPI hardware acceleration to work on Jellyfin I had to mount the GPU.

    devices:
      - /dev/dri:/dev/dri

Do I not have to do that here?

jason

If you want to use VAAPI hardware acceleration, yes, otherwise ETV will fall back to software mode.

trevor

jason I did add that to my compose.yaml but it's still got the ⚠ symbol next to hardware acceleration with the following message, "The following channels use ffmpeg profiles that are not configured for hardware acceleration (Vaapi, Qsv): 1 -ErsatzTV"

My final compose.yaml is the following:

services:
    ersatztv:
      image: jasongdove/ersatztv:latest-vaapi
      container_name: ersatztv
      restart: unless-stopped
      volumes:
          - './media:/media:ro'
          - './config:/root/.local/share/ersatztv'
      tmpfs:
          - '/root/.local/share/etv-transcode'
      ports:
          - '8409:8409'
      environment:
          - TZ=America/New_York
      devices:
          - /dev/dri:/dev/dri

Any ideas?

l72

I have the following in my docker file:

  --device /dev/dri/renderD128:/dev/dri/renderD128

You'll notice I pass in the full path to the device, not just the parent directory. This has worked for me.

trevor

l72 Thanks for your input. The way I mounted it shouldn't be different than what you did. Other than my mount would mount more than what is necessary. I did change my compose to specify /dev/dri/renderD128 directly though.

That didn't fix it. I did get it fixed though. I hadn't gone into my FFMPEG Profiles and told it to use VAAPI or the GPU. I just assumed that since I was using an image that had VAAPI it would do that automatically. Thanks for your help!

jason

trevor Glad you got it figured out. That's exactly the purpose of the warning (pointing you to the ffmpeg profile editor where you can select a hardware acceleration method).

For context, ETV defaults to software mode in all new installs because it will always work, even if the performance isn't optimal.