cyrenbyren 12 Posted February 8, 2018 Posted February 8, 2018 I'm not a docker expert but I don't think it is true that you need to use --network="host". I have not used it and have no connection problems using the default bridge network and exposing the ports. I did notice that under the advanced, hosting setting that the host ip is bound to Emby. I also don't use upnp ro dlna so maybe it has something to do with that. it is not necessary. only if you want emby to know if you are on the "home" network, and use settings that relates to this.
cyrenbyren 12 Posted February 8, 2018 Posted February 8, 2018 (edited) edit2: You should also mention restart policy on the page, and probably default the command to --restart unless-stopped,for obvious reasons. this i agree with. --restart unless-stopped should be in the default run command in the documentation. Edited February 8, 2018 by cyrenbyren
flix42 0 Posted February 10, 2018 Posted February 10, 2018 since yesterday i see the following error in syslog and the container crashing when i try to login using the webinterface: traps: EmbyServer[14140] trap invalid opcode ip:7f7e62a0c2d4 sp:7f7de8930dd0 error:0 in libcoreclr.so[7f7e6277e000+39e000] has there been any change regarding required CPU features? Fedora release 27 4.14.16-300.fc27.x86_64 Docker version 1.13.1, build caba767-unsupported docker run -d --name emby --volume /home/someone/emby/config:/config --volume /mnt/raid/Media:/mnt/share1 --publish 8096:8096 --env UID=1000 --env GID=1000 --env GIDLIST=100 emby/embyserver:latest
alucryd 315 Posted February 11, 2018 Posted February 11, 2018 @@flix42 There has been no change on our end for quite a while. What was the last working version ?
flix42 0 Posted February 11, 2018 Posted February 11, 2018 hard to say, it was working 3 days ago, is there any way to get a speficic version of the docker image? Restartet the container yesterday and got this error. Found this bug report from a few days ago https://github.com/dotnet/coreclr/issues/16052
alucryd 315 Posted February 11, 2018 Posted February 11, 2018 Thanks for the link, it appears to be a bug in the latest runtime. The latest docker container was rebuilt against this runtime 2 days ago, hopefully the fix is live soon so I can push a working version. In the meantime you can try one of the betas, older ones may not have this problematic runtime built-in. My server supports avx 1 and 2 so I can't reproduce, you may try the 3.2.70.10 tag or lower and see if it helps.
linds1234 19 Posted February 15, 2018 Posted February 15, 2018 (edited) Hi All, Sorry if this has been mentioned before, I've read through the thread but I'm reading conflicting info.. I run the mono version of Emby server in a docker container at the moment. Just trying to work out the smoothest way to switch to the .Net docker version. Would it be as simple as: - Pull the new image - Spin up a new container with the new required run commands, GUID/Mount info, (keeping the mount points for the media exactly the same as the mono version) - Point to existing /config and voila....no need to setup libraries / pull down all the metadata Alternatively... If I was to pull the latest image down, then run this on the *existing* mono container: docker exec it emby-srv update Would it then force the update to the Mono version? Because running this command at the moment just updates the server to the newest mono server version (the last image that was pulled from emby/embyserver was ~4 months ago on the docker server, is this why?). Or will my upgrade be easier to use the server backup plugin? Also, I noticed the volume mount syntax is a bit different for the .net Core docker container: --volume /path/to/share1:/mnt/share1 Would this be valid: --volume /path/to/share1: /share1 (does the mount syntax here *need* to have "/mnt" before it? I'm assuming it doesn't...) Thanks for your help and sorry for the 20 questions! Cheers, Lindsay Edited February 15, 2018 by linds1234
mastrmind11 722 Posted February 15, 2018 Posted February 15, 2018 I would think just spinning up a new container and pointing it at the existing mounts/config should be fine. Nice thing about docker is you can try w/o much risk. 2
linds1234 19 Posted February 16, 2018 Posted February 16, 2018 thanks @mastrmind11- I'll give that a shot.
danneboy12 0 Posted February 16, 2018 Posted February 16, 2018 Hi, sorry if I'm posting in the wrong place but my emby container was crashing while not doing anything so I tried completely deleting all traces of it and installed the newest stable one from official emby repo and now it crashes in the first setup screen where it asks me to choose a language. I'm running it in docker on unRAID 6.4.1
Luke 42077 Posted February 16, 2018 Author Posted February 16, 2018 Hi, sorry if I'm posting in the wrong place but my emby container was crashing while not doing anything so I tried completely deleting all traces of it and installed the newest stable one from official emby repo and now it crashes in the first setup screen where it asks me to choose a language. I'm running it in docker on unRAID 6.4.1 Hi there, please attach the emby server log. you can learn how to do that here: https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Thanks.
danneboy12 0 Posted February 16, 2018 Posted February 16, 2018 (edited) Hi there, please attach the emby server log. you can learn how to do that here: https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Thanks. Thanks for the extremely quick reply, I just realized that it only crashes when I use chrome in normal mode on my gaming pc, it doesnt crash when I use Edge or Incognitive mode in chrome on the same pc and neither does it do that on my phone. I assume clearing cache/cookies should help but here is the log anyway. server-63654405050.txt Edited February 16, 2018 by danneboy12
linds1234 19 Posted February 17, 2018 Posted February 17, 2018 I would think just spinning up a new container and pointing it at the existing mounts/config should be fine. Nice thing about docker is you can try w/o much risk. This method has worked, thanks. 1
sebasmiles 8 Posted March 3, 2018 Posted March 3, 2018 Hello, I have been getting some weird crashes lately, no warning it just crashes the docker. I found the docker down a couple times, this last time I actually saw it happen (as I was trying to play a file). I couldn't find anything to tell me whats the issue, below is the output of the Docker log (this is the tail, before this it shows a bunch of the lines similar to where it starts below). I doubt this will be of help, but in case someone else is experiencing similar behavior I am posting. I have since updated to the new 3.3, hopefully it will fix it. 2aaf20ebd000-2aaf20ebe000 ---p 00000000 00:00 0 2aaf20ebe000-2aaf22ba2000 rw-p 00000000 00:00 0 2aaf22ba2000-2aaf24000000 ---p 00000000 00:00 0 7ffd2aa39000-7ffd2aa5a000 rwxp 00000000 00:00 0 [stack] 7ffd2ab15000-7ffd2ab17000 r--p 00000000 00:00 0 [vvar] 7ffd2ab17000-7ffd2ab19000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Aborted [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. server-63655632000.txt
Luke 42077 Posted March 3, 2018 Author Posted March 3, 2018 Hello, I have been getting some weird crashes lately, no warning it just crashes the docker. I found the docker down a couple times, this last time I actually saw it happen (as I was trying to play a file). I couldn't find anything to tell me whats the issue, below is the output of the Docker log (this is the tail, before this it shows a bunch of the lines similar to where it starts below). I doubt this will be of help, but in case someone else is experiencing similar behavior I am posting. I have since updated to the new 3.3, hopefully it will fix it. 2aaf20ebd000-2aaf20ebe000 ---p 00000000 00:00 0 2aaf20ebe000-2aaf22ba2000 rw-p 00000000 00:00 0 2aaf22ba2000-2aaf24000000 ---p 00000000 00:00 0 7ffd2aa39000-7ffd2aa5a000 rwxp 00000000 00:00 0 [stack] 7ffd2ab15000-7ffd2ab17000 r--p 00000000 00:00 0 [vvar] 7ffd2ab17000-7ffd2ab19000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Aborted [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. hi @@sebasmiles, can you update to the latest version of emby server? then try removing the statistics and kodi sync plugins and let us know if the issue persists. Thanks ! 1
ice pube 20 Posted March 11, 2018 Posted March 11, 2018 hi @@sebasmiles, can you update to the latest version of emby server? then try removing the statistics and kodi sync plugins and let us know if the issue persists. Thanks ! I did this and am still getting crashes using unraid. Not sure what else to post, my log snippet like the above user it just hard crashes.
Luke 42077 Posted March 11, 2018 Author Posted March 11, 2018 I did this and am still getting crashes using unraid. Not sure what else to post, my log snippet like the above user it just hard crashes. @@ice pube can you please attach the emby server log? thanks.
aheckel 0 Posted March 13, 2018 Posted March 13, 2018 Hi all, where can I download a fresh emby docker container for aarch64 / armv8? Seems it has been removed from the official respository? Thanks in advance
alucryd 315 Posted March 13, 2018 Posted March 13, 2018 @sebasmiles: Could you please post the whole error, might help pinpoint the source of the issue.
solidus28 12 Posted March 18, 2018 Posted March 18, 2018 Good morning! I'm just transitioning from a Windows server to an Unraid box hosting Emby. I'm using the official Emby, Stable distro for my docker. Working great, but noticed one glitch I just can't figure out. If I go to the 'Logs' Page on the Dashboard, the times underneath each log entry are correct, however, when I open the log up, the timestamps are exactly 4 hours in the future. For example, my dashboard shows 3/18/2018 9:42a on the latest log, but when I open it, the latest entry shows 2018-03-18 13:42:42. Not the biggest deal for reading the logs as I can do the math, but I'm noticing scheduled tasks seem to follow the 4 hour ahead time, not the real time. My Unraid settings seem to show the correct time, my bios also shows the right time (well, I just discovered it wasn't set for daylight savings, so it was one hour, but not 4. I just fixed that). Where else can I look? Anyone else observed this?
Luke 42077 Posted March 18, 2018 Author Posted March 18, 2018 Hi, check and make sure the timezone is set correctly in the docker container.
solidus28 12 Posted March 18, 2018 Posted March 18, 2018 Any chance you could point me in the right direction? I don't see a time setting in the actual Docker settings, nor in the Emby container settings. Unraid that is hosting the Docker is set to Eastern, which is correct and is showing the correct time. Is there somewhere within the Emby docker container? Or something I'm missing in the actual Docker settings?
Luke 42077 Posted March 18, 2018 Author Posted March 18, 2018 See if this helps https://forums.docker.com/t/synchronize-timezone-from-host-to-container/39116&ved=2ahUKEwjN-JCQqvbZAhUESq0KHfJyCD0QFjABegQICRAB&usg=AOvVaw16hNGiJ-VdD6jzL6nSdS66
mastrmind11 722 Posted March 18, 2018 Posted March 18, 2018 Any chance you could point me in the right direction? I don't see a time setting in the actual Docker settings, nor in the Emby container settings. Unraid that is hosting the Docker is set to Eastern, which is correct and is showing the correct time. Is there somewhere within the Emby docker container? Or something I'm missing in the actual Docker settings? Usually timezone is set as an argument to the docker create/run command, like this: -v /etc/localtime:/etc/localtime:ro \ or -e TZ=America/New_York \
solidus28 12 Posted March 18, 2018 Posted March 18, 2018 Thanks. I will have to brush up on my Linux skills [emoji4] Haven't dabbled in several years. Sent from my LGLS992 using Tapatalk
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