VAAPI Failure in Docker

[nateify 0]

On Debian 9.5 with a Docker container for Emby, I cannot get VAAPI to work. The CPU is a Skylake i3-6100 with Intel HD Graphics 530.

 

Output of vainfo:

KiTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused
error: can't connect to X server!
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.3)
vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.7.3
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileH264MultiviewHigh      : VAEntrypointVLD
      VAProfileH264MultiviewHigh      : VAEntrypointEncSlice
      VAProfileH264StereoHigh         : VAEntrypointVLD
      VAProfileH264StereoHigh         : VAEntrypointEncSlice
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileVP8Version0_3          : VAEntrypointVLD
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice

As per the Docker container instructions, I have run the following command: 

getent group video | cut -d: -f3

And the output is 44. In my Docker container settings the GIDLIST is 100,44 as 100 is the GID of the user which has ownership of the media files, which is also in the video group.

 

Here is a snippet of the FFMPEG log from Emby where VAAPI fails:

[AVHWDeviceContext @ 0x17d7940] No VA display found for device: /dev/dri/renderD128.
Device creation failed: -22.
Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Invalid argument
Error parsing global options: Invalid argument

Additionally, the output of ls -al /dev/dri

total 0
drwxr-xr-x  2 root root        80 Jul 28 17:11 .
drwxr-xr-x 18 root root      3080 Jul 28 17:13 ..
crw-rw----  1 root video 226,   0 Jul 28 17:11 card0
crw-rw----  1 root video 226, 128 Jul 28 17:11 renderD128

ffmpeg-transcode-b985628f-54c1-41c8-8455-8ce0b7ff81c3.txt

Edited July 28, 2018 by nscohen01

[nateify 0]

Hm, seems it was fixed so easily by just nuking and redoing all the permissions for my primary user and the media files. No modifications made to the Docker container. A couple other reports on the forum indicate the issue was resolved by re-creating the Emby user and fixing permissions but this is not applicable for the Docker setup. ¯\_(ツ)_/¯

[Luke 37142]

Thanks for the feedback. Something must have changed regarding primary user permissions.