Unable to install emby on Ubuntu 18.04 using docker

[jds_emby 0]

I followed the official guide to install emby in Docker:

 

docker run -d --name=emby --volume /media/virtual/htpc/emby/config:/config --volume /media/virtual:/mnt/share1  --publish 8096:8096 --publish 8920:8920     --env UID=1000 --env GID=100 --env TZ=America/Chicago emby/embyserver:latest

 

It starts up but then shows a bunch of errors in the log file and crashes.  The log file is attached.

 

 

 

embyserver-63713469743.txt

[Luke 36991]

hi there @@jds_emby, I've never seen this error before that's in your server log. I did find this:

 

https://github.com/dotnet/corefx/issues/22415

 

How much memory did you allocate to the container?

[jds_emby 0]

It is my understanding of docker that it has unlimited resources unless otherwise specified, and I have not specified any limitations. 

Apparently it can kill processes if it runs out, but that does not seem to by my case. I have 16G of memory, and it almost never goes above 50% usage, according to glances.

 

EDIT: I double checked this with $docker stats.  All of the containers show a limit of 16G for memory.  Swap is also allowed. 

Edited January 2, 2020 by jds_emby

[Luke 36991]

Did you try installing again on top of your existing version?

[jds_emby 0]

I tried reinstalling.  I deleted and reinstalled.  Both, many times. Same outcome each time.

[tarsosis 0]

What version of Docker are you using?

 

When you did the install did you add the repo for Docker or use the default one that came with Ubuntu 18.04?

[jds_emby 0]

Good question.  I did not find any repo, and the docker version was 18.something, so was plain ubuntu repo.  

I added the docker-ce repo and updated docker to get

$docker --version 
Docker version 19.03.5, build 633a0ea838

Tried again to install the container, but it crashes just the same.

[Luke 36991]

Can you try our native ubuntu package and see how that compares? Thanks.

[jds_emby 0]

I previously had that working, but uninstalled it. Docker still does not work.

[Luke 36991]

Have you configured your system in any non-standard way that we should know about? For example, if we do a fresh install of Ubuntu and Docker at default settings, how does that setup differ from yours?

[jds_emby 0]

It is fairly standard, with one exception. I have pooled several HDs using mergerfs. The container configs and media files are on these. I have experimented a bit with those switches, but nothing changes. I can give you the current settings if you want.

[jds_emby 0]

So, no hope? Just something irreproducible?

[Luke 36991]

I think right now we just don't know as we've never seen this before.

[Luke 36991]

Can you try the beta install?

[jds_emby 0]

Just replaced "latest" in my docker install above with "beta", but no change.

[Luke 36991]

What version do you have? Can you supply a log anyway despite the no change? Thanks.

[jds_emby 0]

Here is the log.  I think that all versions are above.

embyserver-63714173641.txt

[Luke 36991]

Is the main /config folder on a mergefs drive?

[jds_emby 0]

yes

[Luke 36991]

And the /system folder as well?

[jscoys 143]

Hum don’t if it can help but here is a tutorial to run Emby in a container with docker-compose on CentOs 8: https://youtu.be/RthGsZVPdOU

 

Commands for docker/docker-compose are quite the same for all Linux distros.

 

 

Sent from my iPhone using Tapatalk

[jds_emby 0]

I don't know what a /system folder is.  Do you mean / or root folder?

The root folder is not on the mergerfs pool.

[Luke 36991]

/system is actually a path inside the docker container, but you already said that /config is mapped to a path that is on mergefs.

 

I'm wondering if the .NET Core runtime is just not working well with mergefs. Do you need to map /config to a mergefs location?

[jds_emby 0]

Yeah.  I did with this switch: 

--volume /media/virtual/htpc/emby/config:/config

[Luke 36991]

Can you move that so that it's not on a mergefs location. We build Emby Server with .NET Core and it looks to me like something fundamental is just not supported and I don't believe we can do anything about this.