Please add mesa-va-drivers package in the docker image

PeerTube
21

would you kindly test something for me? can you transcode a video that you upload? i’d just like a test that matches my case exactly.

22

i’m starting to think that peertube is too out of date for my hardware. XD

is there a way i can safely base this on trixie instead?

23

got something.

i need mesa-va-drivers from bookworm-backports. this will also pull in mesa-libgallium. i needed both for Owncast.

vainfo

error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can’t connect to X server!
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_17
amdgpu: os_same_file_description couldn’t determine if two DRM fds reference the same file description.
If they do, bad things may happen!
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 25.0.4-1~bpo12+1 for AMD Radeon Graphics (radeonsi, gfx1200, ACO, DRM 3.63, 6.15.4-1-default)
vainfo: Supported profile and entrypoints
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileAV1Profile0 : VAEntrypointEncSlice
VAProfileNone : VAEntrypointVideoProc

24

done, you can retry

ii  mesa-libgallium:amd64 25.0.4-1~bpo12+1 amd64        shared infrastructure for Mesa drivers
1 « J'aime »
25

thanks. even with both mesa-va-drivers and mesa-libgallium from backports, the best i get is the vainfo output. it still fails with:

Error: ffmpeg exited with code 1: Device creation failed: -22.
Failed to set value ‹ /dev/dri/renderD128 › for option ‹ vaapi_device ›: Invalid argument
Error parsing global options: Invalid argument

at ChildProcess.<anonymous> (/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)
at ChildProcess.emit (node:events:524:28)
at ChildProcess._handle.onexit (node:internal/child_process:293:12)
26

too quick, updated my image now, plz retry

1 « J'aime »
27

thanks for all your work on this.

this is improved, but i think this is as far as we can go with bookworm. :confused:

i get vainfo now, but that’s it. otherwise, it has the permissions it needs, so not sure why it isn’t working. the only difference now from Owncast is the version of ffmpeg, but i don’t think we can fix that.

28

indeed I don’t see ffmpeg package in backports : Debian -- Paquets logiciels dans « bookworm-backports »

Here is the dockerfile if it can help you

Dockerfile_peertube

FROM chocobozzz/peertube:production-bookworm
ENV DEBIAN_FRONTEND=noninteractive

RUN echo "Types: deb deb-src\nURIs: http://deb.debian.org/debian\nSuites: bookworm-backports\nComponents: main\nEnabled: yes\nSigned-By: /usr/share/keyrings/debian-archive-keyring.gpg" > /etc/apt/sources.list.d/debian-backports.sources

RUN apt update && apt install mesa-va-drivers/bookworm-backports vainfo intel-media-va-driver mesa-libgallium/bookworm-backports -y
1 « J'aime »
29

i’m going to try my hand at spinning one up based on trixie and see if i can get that to work. i’ll let you know how it goes!

30

ok ! … :wink:

1 « J'aime »
31

trixie ran just fine, but the error remains the same, even with ffmpeg 7. no idea what’s happening or why it works for Owncast, but not Peertube.

32

oh hey, would you mind sharing your base container setup doc? a quadlet or docker compose?

just so i can compare. thanks!

33

hi ! neither :slight_smile: I’m using Nomad (Hashicorp), you can get my setup here : Making sure you're not a bot!

1 « J'aime »