VAAPI build need drivers in container to work

[timsu92]

I'm trying image with tag 7.1-vaapi2404 and also building using docker-images/7.1/vaapi2404/Dockerfile, and I find it can't use Intel video cards.

This can be solved by installing intel-media-va-driver package, and then, we can see the info using vainfo. However, current Dockerfile seems don't want to install any Debian packages in the final image and copy files instead. What might be a better way to solve this?

[timsu92]

I see the original PR adding this feature mentioned that the Intel driver should run the host and not in the container: #106 (comment)

However, while vainfo is running well on host, if I don't have intel-media-va-driver package installed in container, executing ffmpeg directly will show error initializing VAAPI:

[AVHWDeviceContext @ 0x59fc40680700] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
[AVHWDeviceContext @ 0x59fc40680700] Failed to initialise VAAPI connection: -1 (unknown libva error).
Device creation failed: -5.
[AVHWDeviceContext @ 0x59fc40668240] Cannot open the X11 display .
Device creation failed: -1313558101.
[vist#0:0/hevc @ 0x59fc4068cd80] [dec:hevc @ 0x59fc40641640] Auto hwaccel disabled: no device found.

I think we should add it.

[superflyxxi]

Hey guys, I'm seeing the same issue. I used to use VAAPI (with Intel driver) a long time ago, but I stepped away from it. However, I finally got back a nuc that supports hardware encoding. Here are my steps to simulate.

On the host:

vainfo | grep Enc
error: can't connect to X server!
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri-nonfree/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointEncSlice

Do encoding (inside container)
ffmpeg -stats_period 30 -y -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i "file:///pwd/File.mkv" -map 0:0 -c:v:0 h264_vaapi -qp 20 -level:v 4 -metadata:s:v:0 language=eng -metadata "title=Testing inside" -max_interleave_delta 120000000 "file:///pwd/Testing inside.File.mkv.mkv"

This fails with the below error.

[VAAPI @ 0x559bf6781580] Failed to initialise VAAPI connection: -1 (unknown libva error).
Device creation failed: -5.
[vist#0:0/mpeg2video @ 0x559bf675f740] [dec:mpeg2video @ 0x559bf6780a80] No device available for decoder: device type vaapi ne
eded for codec mpeg2video.
[vist#0:0/mpeg2video @ 0x559bf675f740] [dec:mpeg2video @ 0x559bf6780a80] Hardware device setup failed for decoder: Input/outpu
t error

Inside the container, it does not have vainfo. So just apt-get update; apt-get install vainfo.

Run the same exact ffmpeg above and it works fine. I haven't figured out which package is installed with vainfo that causes it to work. But here's the list it finds and installs.

The following additional packages will be installed:
  i965-va-driver intel-media-va-driver libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm2 libelf1t64 libigdgmm12 libllvm20
  libpciaccess0 libsensors-config libsensors5 libva-drm2 libva-wayland2 libva-x11-2 libva2 libwayland-client0 libx11-6
  libx11-data libx11-xcb1 libxau6 libxcb-dri3-0 libxcb-present0 libxcb-randr0 libxcb-sync1 libxcb-xfixes0 libxcb1 libxdmcp6
  libxext6 libxfixes3 libxshmfence1 mesa-libgallium mesa-va-drivers va-driver-all

[superflyxxi]

Probably best to include vainfo just in case? I'll create a PR and let me know your thoughts. My Dockerfile that builds off of this has this workaround for now.

[superflyxxi]

Pinpointed it to va-driver-all dependency. With this in place, ffmpeg with hardware VA-API encoding works.

[timsu92]

@superflyxxi I see va-driver-all depends on intel-media-va-driver, which is the package I found that fixes this problem.
I would like to know whether the problem is fixed with only intel-media-va-driver installed?

[superflyxxi]

To be honest for this project, Intel is not the only VA-API implementation. So best to include all the drivers so that anyone can use the image.