OMV DOCKER EMBY problem with VAAPI

[EODCrafter 181]

Would like to Piggy Back on this if I may........

 

Why is it better to use Software Decoding compared to this? FPS with HW enabled is @5-10 but when I switch it off it jumps to 50-60. Is it cause this GPU is just too old?

 

[Luke 40088]

Are you running Docker on OMV?

[EODCrafter 181]

Are you running Docker on OMV?

No go ahead and delete that, just thought I would slip it in.

Edited February 26, 2019 by EODCrafter

[Luke 40088]

Please open a new topic. Thanks.

[sephx 5]

in docker container devices, just add /dev/dri not a specific number.

permissions should look like this on /dev/dri. they reset on boot.

drwxrwxrwx  2 root root        80 Feb 26 21:52 by-path
crwxrwxrwx  1 root video 226,   0 Feb 26 21:52 card0
crwxrwxrwx  1 root video 226, 128 Feb 26 21:52 renderD128

 

check the user running emby is part of the video group.

add user to video group with usermod -a -G video USERNAME

Edited February 26, 2019 by sephx

[ZiemaF 0]

It looks like everything is ok

But then I do not see the graphics card in EMBY

root@OMV:/dev/dri# id docker

uid=1001(docker) gid=100(users) grupy=100(users),44(video),996(docker)

root@OMV:/dev/dri# ls -l

razem 0

crwxrwxrwx 1 root video 226,   0 lut 25 07:17 card0

crwxrwxrwx 1 root video 226, 128 lut 25 07:17 renderD128

[Luke 40088]

@@ZiemaF did you find the answer?

[ZiemaF 0]

Unfortunately, I gave up.

I can not run it on OpenMediaVault 4.0.

I am now waiting for OMV5.0, it will be on Debian 10, then maybe it will work.

On windows 10 and windows server 2019 it works perfectly (I installed myself for testing for a moment)

Overall, I'm very happy with the EMBY server on OMV through Docker

I also recommend OMV to everyone, a great solution for the home server.

[Luke 40088]

Thanks for the feedback.

[Riggs 303]

https://www.youtube.com/watch?v=Rbee3Se24Ms

[Luke 40088]

https://www.youtube.com/watch?v=Rbee3Se24Ms

 

What is this?

[Riggs 303]

What is this?

 

 

Installing Emby, a Plex alternative, in Openmediavault

[Luke 40088]

Thanks for providing that !

[scheideggstrasse 0]

On 3/19/2019 at 8:40 AM, ZiemaF said:

Unfortunately, I gave up.

 

I can not run it on OpenMediaVault 4.0.

 

 

I am now waiting for OMV5.0, it will be on Debian 10, then maybe it will work.

 

 

On windows 10 and windows server 2019 it works perfectly (I installed myself for testing for a moment)

 

 

Overall, I'm very happy with the EMBY server on OMV through Docker

 

 

I also recommend OMV to everyone, a great solution for the home server.

 

have you tried running it at root (not good, but worth a test)

docker run -d --privileged   --volume /var/lib/emby-docker/:/config --device /dev/dri/:/dev/dri/ --publish 8096:8096 --publish 8920:8920 --env UID=0 --env GID=0 --env GIDLIST=0 emby/embyserver:latest

 

[bgeneto 0]

On 2/25/2019 at 8:55 AM, sephx said:

Not sure if you got this problem fixed. Others mentioned adding devices, nobody mentioned /dev/dri permissions?

 

If use portainer to manage docker. Edit Emby, find Runtime & Resources Tab. Add Device - > /dev/dri Rebuild your container.

Permissions so container can talk to igpu = chmod -R 777 /dev/dri (rebuilt on server boot, best to add in to compose/boot scripts)

 

Hope that helps!

Spent several hours trying to figure out why adding GIDs from "video" (44) and "render" (107)  groups to GIDLIST in docker-composer.yml does not work. 

I think there is a problem with permissions specific to the "renderD128" device owned by root:render in Debian Buster host. I've double checked the GIDLIST and it has the correct GIDs from "video" and "render" groups. But still getting error Message: "Failed to open the drm device /dev/dri/renderD128".

I gave up since the permission trick did the job. Unfortunately this is only a temporary workaround. For a permanent workaround I suggest creating a new udev rule, say: 

/etc/udev/rules.d/99-dri.rules

with the following contents: 

KERNEL=="card[0-9]*", GROUP="video", MODE="0666"
KERNEL=="renderD*", GROUP="video", MODE="0666"

Reboot the host machine and voila! vaapi with Intel Graphics HD working properly via emby docker container. 

[Luke 40088]

@bgeneto that's great info, thanks for sharing.