just finished Into the Dark, my third The High Republic book!

it was EXCELLENT.

first half is really setup, but the second half REALLY PUNCHES!

fantastic book, and REALLY brought me in to the era. excellent explorations of the Jedi as well.

i want to collect these now.

Hello all!

As part of my effort to troubleshoot my issues with this, I'm looking for some more data.

Do YOU run containerized Peertube, have an AMD Radeon RX 9000 series GPU, AND successfully use VAAPI hardware accelerated encoding?

If so, please reply and tell me about your setup. Rootful or Rootless, your quadlet or compose file, group IDs and permissions, and anything else you think may be helpful.

Thank you!

he looks BRUTAL! The Emperor Returns!

SO good to hear 13 again! very happy to have her back!

my goto spot for SNK data, primarily KoF and FF.

what do you think? are you in on nuMAHVEL!?

The KING! Tiger Uppercut!

Will be held in Nice.

Are you going?!

He looks AMAZING!

i’m starting to think it’s the debian base of this container image. it may just be too out of date for my GPU.

i think i'm giving up on this for now.

thanks all!

hey all!

for the life of me, i cannot get VAAPI hardware accelerated encoding to work. i always get this error:

Error: ffmpeg exited with code 234: 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)

• AMD Radeon RX 9060 XT
• the peertube vaapi transcoding plugin is installed
• i have mesa-va-drivers and mesa-libgallium installed from bookworm backports.
• the container is rootful.
• /dev/dri is mapped
• the render group id matches between host and container.
• SELinux is set to allow containers access to devices.

no joy.

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

i've also tried updating the packages from trixie and sid, and installing the firmware-linux-nonfree.

i've tried disabling SELinux. i've tried making the container permissive.

no change.

any help is appreciated! thank you!

i’m starting to think it’s the debian base of this container image. it may just be too out of date for my GPU.

i just ended up going with a new image with the components installed, which i've been informed is best practice.

i just ended up going with a new image with the components installed, which i've been informed is best practice.

Hey there!

i have an Owncast container that needs two extra files added to it every time it starts up because the base image doesn't include them. they can be downloaded from within the container. i just need a way to tell the container to always do that when it starts up.

i've tried adding this to my quadlet:

[Container]

Exec=apk update && apk add --no-cache mesa-va-gallium mesa-dri-gallium

but it doesn't work.

does anyone know how to correctly automate this?

thanks!