Problems with Docker?

[IceBoosteR 10]

Hi there,

 

I am using Emby on an Ubuntu VM and everything works fine.

Due to nw hardware I want to make the switch and move to Docker. therefore I have installed ubuntu server 18.04 and docker of course, letting emby run with the following settings:

docker run -d --restart unless-stopped --volume /docker/Emby:/config --volume /mnt/movies:/mnt/movies --device /dev/dri/renderD128 --publish 8096:8096 --publish 8920:8920 --env GIDLIST=44 emby/embyserver:latest

But I do see problems with the docker  configuration. Firsrt of all, I am using an Intel NUC (NUC7PJYH), which is able to handle 4K. Regardless of which video I start, 1 core is getting on 100% CPU utilisation, even if a movie has 360p, 480p I think this might be a bug. FFMPEG is using the horsepower only.

On the other handside I have activated hardware acceleration (VAAPI) to use the power of the integrated Intel graphics. Therefore I have added the render node , and added the video group in the GID list.This should be all I thought.

And finally, I do see errors in the logs. First, every movie I play is generation a "remux" file, which is not created when I run the same movie on the "old" system.

 

I have not installed any additional graphics driver (like https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers ), because I suggesated that the latest one will be installed by apt itself.

root@athene:~# lspci -nnk | grep -iA2 vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3184] (rev 03)
        Subsystem: Intel Corporation Device [8086:2072]
        Kernel driver in use: i915

Or od I need something like: https://launchpad.net/ubuntu/+source/intel-vaapi-driver

 

I have attached the logfile of the error messages. Maybe its my fault, maybe its not.

I would be happy if you guys can help me here.

Thanks!

-Ice

Edited August 4, 2018 by IceBoosteR

[Luke 42079]

Hi there, did you forget to attach the log file? Thanks.

[IceBoosteR 10]

Hi Luke,

 

yes

But this thime is is attached, I promise

(I haven't seen the "attach this file" button need to be pressed aswell...)

logfile emby.txt

Edited August 5, 2018 by IceBoosteR

[Luke 42079]

And the ffmpeg log?

[IceBoosteR 10]

Hi,

 

wasn't aware that you need those too. I have uploaded all logs created by one playback.

Password in PM.

logs.zip

[Luke 42079]

We pushed an update to our docker container earlier today to resolve an issue unrelated to this. Try updating and see if that helps here. Thanks.

[IceBoosteR 10]

Hi Luke,

 

I have checked this today with the latest version. The problem still appears.

[IceBoosteR 10]

Could I please have an update? :/

 

On the other side, maybe a user can verify that my docker command is correct and I do not miss anything.

That would be great.

 

-Ice

[Luke 42079]

We're looking into this, thanks.

[IceBoosteR 10]

We're looking into this, thanks.

Thanks for the feedback Luke.

[alucryd 315]

What are the owner:group and permissions of the render node /dev/dri/renderD128 on your base system?

[IceBoosteR 10]

What are the owner:group and permissions of the render node /dev/dri/renderD128 on your base system?

Hi @@alucryd,

it is:

root@athene:~# ls -lisa /dev/dri/renderD128
331 0 crw-rw---- 1 root video 226, 128 Aug 17 20:32 /dev/dri/renderD128

Where root has of course ID 0 and the video group is 44:

video:x:44:

[IceBoosteR 10]

Bump....

[alucryd 315]

Apologies for the delay. I don't have a vaapi capable cpu in my server anymore, but from what I can tell your docker run command is fine and permissions on the render node look fine as well.

 

Could I get a glimpse of those ffmpeg logs as well?

 

The intel driver is bundled in our docker image, this shouldn't be the issue. Still can you try:

chmod 777 /dev/dri/renderD128

and restart docker to rule this out?

[IceBoosteR 10]

Apologies for the delay. I don't have a vaapi capable cpu in my server anymore, but from what I can tell your docker run command is fine and permissions on the render node look fine as well.

 

Could I get a glimpse of those ffmpeg logs as well?

 

The intel driver is bundled in our docker image, this shouldn't be the issue. Still can you try:

chmod 777 /dev/dri/renderD128

and restart docker to rule this out?

Hi,

no problem.

 

Thats good to hear. I will need some time to do it (not at home right now, but I will upload one as soon as I can.

Normally I would not like to change anything to 777, else I would guess to see an "access denied" message if it is something with the permission.

 

Cheers,

Ice

 

(I do apreciate the effort which has been done in the docker version and of course also in Emby itself!)

[alucryd 315]

I understand, 666 would be enough as well, that's what we went with on arch linux. That render node is not critical, it doesn't really need to be protected. FYI, I'm going on vacation with little to no internet access this evening for about a week. I'll get back to you when I come back home.

[IceBoosteR 10]

So I do see in the current version that now all 4 cores are used. Iam still investigating why the playback on my TV is stutters, because CPU is no more used as 30% over all.

I am looking into this if this is maybe due to the render node.

Disabled the render node and it was even worse.

Edited October 3, 2018 by IceBoosteR

[Luke 42079]

Let us know how you get on. Thanks !

[IceBoosteR 10]

Hi Luke,

as I said previously, when I change from VAAPI to no hardware encoding, the video playback stops every second and needs a second to load. With VAAPI it is only every third second.

But this is only true when I chhose Dolby Atmos /True-HD as soundtrack. DTS and normal DD is fine.

[Luke 42079]

Can we look at the ffmpeg log from an example? thanks.

[IceBoosteR 10]

@@Luke of course. I will generate those when I am home!

[IceBoosteR 10]

@@Luke

As requested the transcoding log. I have used VAAPI as mentioned, it is much smoother as without but still unwatchable.

But this is "only" TRUE-HD not Atmos as far as I can see it.

emby remux log.txt

Edited October 7, 2018 by IceBoosteR

[Luke 42079]

This particular example wont' make any difference with vaapi on or off because no video transcoding is occurring.

[IceBoosteR 10]

Interesting. But there is a difference in playback...

-Ice

[Luke 42079]

We'll have an updated ffmpeg with the next release. I would try again with that. Thanks.