media-driver VS docker-mods

You might need to install the non-free intel media driver: https://github.com/intel/media-driver

Intel had VP9 decode since Kaby Lake (7th gen); original Skylake (6th gen) could not handle it (see here).

I've heard intel-media-driver was the way to go for supported hardware, but I also heard that it could decode slower than libva-intel-driver (like #925), and that Intel doesn't officially support some kind of decode feature in intel-media-driver, but it's implemented in libva-intel-driver.

I reproduced the issue on my end and opened a ticket to let intel devs know. https://github.com/intel/media-driver/issues/1628

I can see 22.6.6 was released in December ( Releases · intel/media-driver (github.com) ), but I'm having troubles getting it installed.

You should be able to choose FFmpeg VAAPI encoder, though it is suggested that kernel 6.2 is needed for this to actually work. I can confirm that it's broken with my A770, while I can choose the device, encoder is failing. No such problem with my Rapter Lake iGPU.

On GitHub there are similar problems reported: https://github.com/intel/media-driver/issues/1282

Source: https://github.com/intel/media-driver/blob/master/docs/media_features.md

Have you tried adding the OpenCL-Intel Dockermod for the LSIO container? I don't believe it'll function properly without it...fair warning it significantly increases startup time. Additionally, it may not matter if you've already verified your hardware acceleration is working as expected, but at one point I did have to specifically indicate both renderD128 and card0 to get everything settled. If it ain't broke, don't fix it, but that's a difference in our compose files I spotted immediately.

Misc - LinuxServer.io images now support mods with multi-digest layers (https://github.com/linuxserver/docker-mods/pull/577)

Are you using a linuxserver container? If so, check this out as well: https://github.com/linuxserver/docker-mods/tree/jellyfin-opencl-intel

If you are running using the lsio container, you could try out this repo which makes the par2 process 2-3 times faster. https://github.com/linuxserver/docker-mods/tree/sabnzbd-par2cmdline-turbo

If you're using the LinuxServer plex image, you're probably facing this issue. https://github.com/linuxserver/docker-mods/issues/575

Following this issue and looking at the code here it appears that the mod identifies running applications on swag by globbing all the conf files (including samples!) and attemting a connection on them. And it does this with ThreadPoolExecutor(max_workers=100) which seems to explain why those DNS queries were being spammed on pihole.

I run a similar set up, but i run jellyfin with linuxserver's docker with this addon: https://github.com/linuxserver/docker-mods/tree/jellyfin-amd