Playback error with docker container

[alc86 0]

Hi,

Today i tried to use Emby on my Qnap NAS but I am struggling with the transcoding. The idea is to use the emby docker container (official) with the container station. The server runs without problems but transcoding does not work.
NAS: TS-431XeU with latest versions of QTS and container station.
Emby Docker container from docker hub.

I have also attached the screenshot of the Log file and the error message.

[Luke 39988]

Hi, is this arm32v7?

[alc86 0]

Hi Luke,

 

I think so the processor type is an AnnapurnaLabs, an Amazon company, Alpine AL-314 Quad-Core 1.7 GHz.

[Luke 39988]

Ok. did you follow the instructions on our website for arm32v7 docker? Because it's actually a different docker image then the one you appear to be using:

 

https://emby.media/download

[alc86 0]

I know that there is a different docker image for arm32v7. This is the one which I have already installed. Ther server i running well only the playback does not work.

[Luke 39988]

hi @@alc86, based on your log i can tell you aren't running the one that I linked to.

[alc86 0]

ok sorry. I use the container station on my QNAP and have selected the emby/embyserver image with the arm32v7 architecture. So which one from docker hub should I use ?

[Luke 39988]

You would use the fourth image in that list there, or the neon version if your cpu supports neon optimzations.

[alc86 0]

so i tried it with both arm docker images but i always get the following error at startup: Failed to initialize CoreCLR, HRESULT: 0x80004005 

[Luke 39988]

can you please attach the complete output? thanks.

[alc86 0]

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.                                                                                                                                                                                                                                              

[s6-init] ensuring user provided files have correct perms...exited 0.                                                                                                                                                                                                                                                      

[fix-attrs.d] applying ownership & permissions fixes...                                                                                                                                                                                                                                                                    

[fix-attrs.d] done.                                                                                                                                                                                                                                                                                                        

[cont-init.d] executing container initialization scripts...                                                                                                                                                                                                                                                                

[cont-init.d] done.                                                                                                                                                                                                                                                                                                        

[services.d] starting services                                                                                                                                                                                                                                                                                             

[services.d] done.                                                                                                                                                                                                                                                                                                         

Failed to initialize CoreCLR, HRESULT: 0x80004005                                                                                                                                                                                                                                                                          

[cont-finish.d] executing container finish scripts...                                                                                                                                                                                                                                                                      

[cont-finish.d] done.                                                                                                                                                                                                                                                                                                      

[s6-finish] syncing disks.                                                                                                                                                                                                                                                                                                 

[s6-finish] sending all processes the TERM signal.                                                                                                                                                                                                                                                                         

[s6-finish] sending all processes the KILL signal and exiting.

Edited February 6, 2018 by alc86

[alc86 0]

Any idea how to solve this problem ?

[Luke 39988]

Hi, we're looking into it, thanks.

[alucryd 238]

Both arm32v7 docker containers use hardware floating point (armhf). You qnap device is most likely arm soft float like almost every NAS out there, unfortunately the dotnet runtime doesn't support soft-float arm yet so we can't provide a container for this architecture.

[Luke 39988]

@@alc86

 

We have instructions for your device on our website:

https://emby.media/nas-server.html

 

Have you seen those?

[alc86 0]

Hi,

 

Now I have installed Qmono + ffmpeg + emby on my NAS from the offical Qnap Forum and I still get the "System.Exception: Error starting ffmpeg".

 

Qmono : Qmono TS-X41 (this is the only one which was posible to install) Version 5.4.1.6.0

ffmeg: ffmpeg_3.4.0_armx41 (this is the only one which was posible to install) Version 3.4.0

Emby: Emby TS-NASARM Version 3.2.70.0

 

I have set the FFmpeg path to /mnt/ext/opt/medialibrary/bin/ffmpeg.  

emby_server.txt

FFmpeg_log_1.txt

FFmpeg_transcode_2.txt

FFmpeg_transcode_3.txt

[Luke 39988]

the ffmpeg build appears to be extremely old:

ffmpeg version 2.8.5 Copyright (c) 2000-2016 the FFmpeg developers

and is potentially missing libraries:

No decoder for stream #0:1, filtering impossible
Error opening filters!

[alc86 0]

I have changed the ffmpeg path to /share/CACHEDEV1_DATA/.qpkg/Qffmpeg/bin/ffmpeg where version 3.3.4 is installed. Still have the same issue.

emby_server.txt

FFmpeg_transcode_1.txt

FFmpeg_transcode_2.txt

FFmpeg_transcode_3.txt

[Luke 39988]

Based on the fact that ffmpeg is not printing anything to the log, from past experience this looks to be permissions related. In other words, the emby server process does not have permission to read that file.

[alc86 0]

@@alucryd

 

Any idea why the first docker image was running well beside the playback ? This image I have downloaded from docker hub emby/embyserver and I have selected arm version. Last week this was availible but now only 3.2.70, beta and latest options are there.

[alc86 0]

which file and how can I set the permissions ?

[alc86 0]

Now I have set the permissions from all directories and files to 777. Still the same error.

[Luke 39988]

Unfortunately as this is the community package I'm just not sure. Can you try asking the question here:

https://forum.qnap.com/viewtopic.php?f=320&t=109476

 

And seeing how they are setting up ffmpeg for your device? Thanks.

[alucryd 238]

@@alc86 We now have separate repositories per architecture. You can use emby/embyserver_arm32v7 or emby/embyserver_arm32v7_neon if your cpu supports neon optimizations, but they probably won't work as I'm pretty sure all qnap devices are soft float. Was the previous image you're referring to mono-based? In that case it was probably soft float, but unfortunately it's not possible with dotnet core yet.

Edited February 11, 2018 by alucryd

[Luke 39988]

@@alc86 We now have separate repositories per architecture. You can use emby/embyserver_arm32v7 or emby/embyserver_arm32v7_neon if your cpu supports neon optimizations, but they probably won't work as I'm pretty sure all qnap devices are soft float. Was the previous image you're referring to mono-based? In that case it was probably soft float, but unfortunately it's not possible with dotnet core yet.

 

Yes it was mono based, so he will have to stick with the QNAP community package for now.