ivolanski 0 Posted January 26 Share Posted January 26 Hello, First of all, thanks in advance for any help you can give me and feel free to ask anything else if you need more information. Emby docker just stop after few seconds, here are some information: It's a N1 box running Openwrt and it contains docker. Quote docker run -d \ --volume /mnt/sda3/tmp/emby/config:/config \ --volume /mnt/sda3/Midia/Filmes:/mnt/share1 \ --device /dev/dri \ --publish 8096:8096 \ --publish 8920:8920 \ --env UID=0 \ --env GID=0\ --env GIDLIST=100 \ emby/embyserver_arm64v8:latest Quote Hostname OpenWrt Model Phicomm N1 (CpuMark : 18568.665377 Scores) Architecture ARMv8 Processor rev 4 (v8l) x 4 Firmware Version OpenWrt R20.7.20 / LuCI Master (git-20.190.41443-b753998) Kernel Version 5.7.10-flippy-40+ Local Time Tue Jan 26 17:59:46 2021 Uptime 6d 2h 9m 58s CPU状态 1512Mhz / 51.0℃ Quote stdout: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. stdout: [s6-init] ensuring user provided files have correct perms...exited 0. stdout: [fix-attrs.d] applying ownership & permissions fixes... stdout: [fix-attrs.d] done. stdout: [cont-init.d] executing container initialization scripts... stdout: [cont-init.d] done. stdout: [services.d] starting services stdout: [services.d] done. stderr: Failed to create CoreCLR, HRESULT: 0x80004005 stdout: [cont-finish.d] executing container finish scripts... stdout: [cont-finish.d] done. stdout: [s6-finish] waiting for services. stdout: [s6-finish] sending all processes the TERM signal. stdout: [s6-finish] sending all processes the KILL signal and exiting. stdout: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. stdout: [s6-init] ensuring user provided files have correct perms...exited 0. stdout: [fix-attrs.d] applying ownership & permissions fixes... stdout: [fix-attrs.d] done. stdout: [cont-init.d] executing container initialization scripts... stdout: [cont-init.d] done. stdout: [services.d] starting services stdout: [services.d] done. stderr: Failed to create CoreCLR, HRESULT: 0x80004005 stdout: [cont-finish.d] executing container finish scripts... stdout: [cont-finish.d] done. stdout: [s6-finish] waiting for services. stdout: [s6-finish] sending all processes the TERM signal. stdout: [s6-finish] sending all processes the KILL signal and exiting. Link to comment Share on other sites More sharing options...
ivolanski 0 Posted January 27 Author Share Posted January 27 UP No one? Link to comment Share on other sites More sharing options...
ivolanski 0 Posted January 28 Author Share Posted January 28 UP Link to comment Share on other sites More sharing options...
ivolanski 0 Posted January 29 Author Share Posted January 29 Help ! Link to comment Share on other sites More sharing options...
MRobi 149 Posted January 29 Share Posted January 29 I've got no idea what the issue is, I'm still learning docker and linux as a whole after moving from FreeNAS. I'd start troubleshooting a few different ways. I'd try the 32-bit image to see if that works. I'd also look at the linuxserver.io image. While not the official emby image, they compile some of the most trusted and reliable images out there. https://hub.docker.com/r/linuxserver/emby Link to comment Share on other sites More sharing options...
Luke 28697 Posted February 4 Share Posted February 4 @ivolanski are you still having an issue with this? Link to comment Share on other sites More sharing options...
ivolanski 0 Posted February 4 Author Share Posted February 4 7 hours ago, Luke said: @ivolanski are you still having an issue with this? Yes, nothing changed I tried many buids, tags... still not working Link to comment Share on other sites More sharing options...
BAlGaInTl 271 Posted February 4 Share Posted February 4 I did a quick search for: Emby Docker Failed to create CoreCLR, HRESULT: 0x80004005 I found quite a few results. I don't have time to go through all of them. I also found some references to JellyFin which is a fork of an older version of Emby. Is this a brand new install? Or an existing one? It seems that it could be a corrupted file somewhere in config. In one instance it was an issue with permissions on the transcoding directory. It could be permissions in general. Link to comment Share on other sites More sharing options...
ivolanski 0 Posted February 4 Author Share Posted February 4 (edited) Hello. I tried many things, one of them was to perform a brand new firmware on the machine and start from scratch. I also probably read the same resources as you and tried set permission on some folders as /driver/dri (or something like this) but no success. Thanks for your time and the help you are giving. Edited February 4 by ivolanski Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now