Emby Netcore Container crashing on several Intel CPU´s

[b0mb]

Hi!

 

The new docker Emby docker container based on netcore is crashing very fast on some intel cpus´s like celeron n3050, j3455 or pentium g4560.

 

I´ve found some workaround like deactivating port mapping and change standard port from 8096 to 8888 but meanwhile i think this problem is related to unRAID or it´s kernel.

 

I tried the same container now on openmediavault where it´s running like a charm.

 

So i guess the only difference compared with unRAID should be the kernel.

 

Is it possible to install a backport kernel on unRAID like on OMV or does some1 have another idea?

 

Thx in advance!

 

b0mb

 

 

[hi2hello]

I can confirm this problem. Same here with newest version of Unraid and (as of today) up-to-date-version of Emby Server (3.3.0) on an Pentium G4560.
Any help kindly appreciated.

 

This is what i get from the unRAID Log right before the Emby Container stops:

Date Time ServerName kernel: traps: EmbyServer[28326] 
trap invalid opcode ip:153485a522d4 sp:153470441a30 
error:0 in libcoreclr.so[1534857c4000+39e000]

Followed by the Emby Log after the container stopped:

Illegal instruction
[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 27, 2018 by hi2hello

[hi2hello]

Any news on that? 
As the netcore version of emby got the main version for quiet some time now, this topic might be a bit more of interest to a bigger amount of users. 

Thought a bump might be worth a try. 
Thanks for any kind of response. 

Edited February 27, 2018 by hi2hello

[Guzzi]

I have the same issue, running on a Pentium G4600 - also waiting for a solution...