Problem with new Emby Net Dot Container

[b0mb]

Hi!

 

I am running  this container on latest unRAID build actually.

 

The old mono Container is running without any problem in host mode.

 

The new Net Dot Container must first be configures in bridged mode.I´ve forwared Port 8888 to 8096 which is emby standard port.

 

After doing this i´ve changed the port in emby backend from 8096 to 8888 and switched the container from bridge to host mode. Now the container works in host mode on port 8888.

 

If i run the container in host mode without changig ports it crashed immediately after openening the wizard.

 

It would be nice if some1 with skills could proof this problem. It might be kernel related i guess because other users do have the same problem on unraid but on OMV with Pentium G4560 it is running fine. My CPU is J3455 btw.

 

Thx in advance!

 

b0mb

[b0mb]

Pls can someone test this. Meanwhile several places with the mentioned cpus wrote in Emby or other forums with the same problem like me. An i3 cpu seems to run well btw....

Gesendet von meinem Redmi Note 3 mit Tapatalk

[b0mb]

ok... this is what i´ve found in docker.log

 

maybe it helps

 

Dec 29 06:23:16 twilight kernel: traps: EmbyServer[29269] trap invalid opcode ip:14769a8dd2d4 sp:1475dba5bbc0 error:0 in libcoreclr.so[14769a64f000+39e000]
Dec 29 06:24:14 twilight kernel: docker0: port 8(vethfb7a602) entered blocking state
Dec 29 06:24:14 twilight kernel: docker0: port 8(vethfb7a602) entered disabled state
Dec 29 06:24:14 twilight kernel: device vethfb7a602 entered promiscuous mode
Dec 29 06:24:14 twilight kernel: IPv6: ADDRCONF(NETDEV_UP): vethfb7a602: link is not ready
Dec 29 06:24:14 twilight kernel: eth0: renamed from vetha0c2e55
Dec 29 06:24:14 twilight kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfb7a602: link becomes ready
Dec 29 06:24:14 twilight kernel: docker0: port 8(vethfb7a602) entered blocking state
Dec 29 06:24:14 twilight kernel: docker0: port 8(vethfb7a602) entered forwarding state
Dec 29 06:24:16 twilight avahi-daemon[11152]: Joining mDNS multicast group on interface vethfb7a602.IPv6 with address fe80::6855:4eff:fe41:5c4a.
Dec 29 06:24:16 twilight avahi-daemon[11152]: New relevant interface vethfb7a602.IPv6 for mDNS.
Dec 29 06:24:16 twilight avahi-daemon[11152]: Registering new address record for fe80::6855:4eff:fe41:5c4a on vethfb7a602.*.
Dec 29 06:26:10 twilight kernel: traps: EmbyServer[31641] trap invalid opcode ip:14d7ff0302d4 sp:14d73fdc5bc0 error:0 in libcoreclr.so[14d7feda2000+39e000]
Dec 29 06:26:14 twilight kernel: docker0: port 8(vethfb7a602) entered disabled state
Dec 29 06:26:14 twilight kernel: vetha0c2e55: renamed from eth0
Dec 29 06:26:14 twilight avahi-daemon[11152]: Interface vethfb7a602.IPv6 no longer relevant for mDNS.
Dec 29 06:26:14 twilight avahi-daemon[11152]: Leaving mDNS multicast group on interface vethfb7a602.IPv6 with address fe80::6855:4eff:fe41:5c4a.
Dec 29 06:26:14 twilight kernel: docker0: port 8(vethfb7a602) entered disabled state
Dec 29 06:26:14 twilight kernel: device vethfb7a602 left promiscuous mode
Dec 29 06:26:14 twilight kernel: docker0: port 8(vethfb7a602) entered disabled state
Dec 29 06:26:14 twilight avahi-daemon[11152]: Withdrawing address record for fe80::6855:4eff:fe41:5c4a on vethfb7a602.
Dec 29 06:32:48 twilight kernel: traps: EmbyServer[13360] trap invalid opcode ip:14eb98b4b2d4 sp:14eb7e200bc0 error:0 in libcoreclr.so[14eb988bd000+39e000]