Docker QSV

[aahmyu 9]

Hello,

Yesterday I migrated my server to Ubuntu and have all my stuff running inside docker including emby.

My only issue is not being able to enable intel QSV

Is it not supported? I'm using emby official latest beta docker image

this is the graphic card info:

*-display
       description: VGA compatible controller
       product: UHD Graphics 630 (Desktop)
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:126 memory:a0000000-a0ffffff memory:90000000-9fffffff ioport:4000(size=64) memory:c0000-dffff

 

Inside /dev/dri I have these files: 

drwxr-xr-x  2 root root         80 jul 20 18:11 by-path
crw-rw----+ 1 root video  226,   0 jul 20 18:11 card0
crw-rw----+ 1 root render 226, 128 jul 20 18:11 renderD128

this is what I get in the hardware detection log in emby:

"Devices": [
{
"DeviceIndex": 0,
"DeviceInfo": {
"VendorName": "Intel Corporation",
"DeviceName": "UHD Graphics 630 (Desktop)",
"SubsytemVendorName": "ASUSTeK Computer Inc.",
"VendorId": 32902,
"DeviceId": 16018,
"SubsytemVendorId": 4163,
"SubsytemDeviceId": 34452,
"DevPath": "/sys/bus/pci/devices/0000:00:02.0",
"DrmCard": "/dev/dri/card0",
"DrmRender": "/dev/dri/renderD128",
"IsEnabled": 1,
"IsBootVga": 1,
"Error": {
"Number": -1,
"Message": "Failed to open the drm device /dev/dri/renderD128"
}
}
}
],
"Log": [
{
"Level": 40,
"Category": 0,
"Message": "Found 13 device entries"
}
]

 

This is my emby docker-compose.yml:

  emby:
    container_name: emby
    image: emby/embyserver:beta
    ports:
      - '8096:8096'
    environment:
      - UID=1000
      - GID=1000
      - GIDLIST=1000
    volumes:
      - ./emby/programdata:/config
      - /mnt/ds418j:/ds418j
    devices:
      #- /dev/dri/renderD128:/dev/dri/renderD128
      #- /dev/dri/card0:/dev/dri/card0
       - /dev/dri:/dev/dri

 

This is my user groups: adm cdrom sudo dip video plugdev render lpadmin lxd sambashare

 

the "id user" command shows that my uid is 1000 and gid is 1000 which im using in docker.

I tried doing this too "

chmod -R 777 /dev/dri

also didn't work.

Can someone help me get this running? What am I missing? 

Regards

[aahmyu 9]

I switched to the linuxserver image and i got vaapi working.

Edited July 20, 2020 by aahmyu

[Luke 37272]

How did you setup that other image?

[aahmyu 9]

3 hours ago, Luke said:

How did you setup that other image?

Exactly the same as I setup the official image:

emby:
    image: linuxserver/emby:beta
    container_name: emby
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Amsterdam
    volumes:
      - ./emby/programdata:/config
      - /mnt/ds418j:/ds418j
    ports:
      - 8096:8096
    devices:
      - /dev/dri:/dev/dri
    restart: unless-stopped

It just worked and got the Vaapi stuff listings. Maybe the official one is missing some stuff.

[wedgekc 12]

I believe your issue is the GIDLIST values.  You need to use both numbers from the commands below in your docker-compose:

getent group video | cut -d: -f3

getent group render | cut -d: -f3

i.e. - "GIDLIST=44,109"

Edited July 21, 2020 by wedgekc

[aahmyu 9]

28 minutes ago, wedgekc said:

I believe your issue is the GIDLIST values.  You need to use both numbers from the commands below in your docker-compose:

getent group video | cut -d: -f3

getent group render | cut -d: -f3

i.e. - "GIDLIST=44,109"

Yep this fixes it. Thanks.

[mastrmind11 717]

literally outlines this on the official docker setup page.

[Holtz 0]

As I have the same problems I decided to take advantage of this topic.
I have a J1800 where it supports QSV and I even use it on Plex.
When checking the transcoder options I realized that it was not being identified.
After realizing that I needed to change the GIDLIST values.
According to the images, I managed to activate it but I don't know if anything else is missing.
Do I need to change anything else?

 

hardware_detection-63745416011.txt

Edited January 5, 2021 by Holtz

[Luke 37272]

Based on the screenshots it looks like you're good to go, no?

[Holtz 0]

13 hours ago, Luke said:

Based on the screenshots it looks like you're good to go, no?

It seems to me that everything is working well, I was just in doubt about the group render relationship that did not return value and the transcoder appears as VAAPI and not QSV, is this correct? Should I see the QSV together in the options?

[Luke 37272]

Docker is currently vaapi only for intel but we may add QSV in future updates. Thanks.