Unraid Emby server docker seems to be filling up docker image.

[apgood 0]

The Emby server docker on unraid seems to be filling up my docker image, which results in my other dockers becoming unresponsive/ reporting errors.

If I stop the Emby docker and then turn the docker feature in unraid off then on seems to fix the issue.

 

The /config host location is /mnt/cache/appdata/menu and /mnt is /mnt/user

 

Docker image size 60gig with 9.04 gig used.

 

If I leave the emby docker off I don't have any issues, but if I turn it on then the issue appears in a day or two.

 

Anecdotally it seems to be related to when I've played something on my htpc or some other device.

 

Could some sort transcoding temp file be filling up the docker image?

 

Suggestions of things I could check / try to stop this happening?

[Luke 42077]

Possibly. have you taken a look at the contents to see what folders are the largest?

[apgood 0]

Thanks Luke. I only shared one folder that has about 1100 bluray movies in it. A mix of iso, mkv and folder rips. Note most of the movies are just in the one folder (i.e. each movie isn't in its own folder). Is this likely to be the issue?

[Luke 42077]

I guess what I mean is, you said that a certain folder was taking up a lot of space, so did you look inside the folder to see where most of it is being used?

[apgood 0]

Sorry. I meant that the emby docker seems to filling up all the free space in my docker.img in unraid and killing my other dockers for some reason.

 

Not sure how how to check what file or folder within the emby docker is chewing up all the space.

[Capt.Insano 3]

No such problems here, I've been using Emby within unRAID docker for months now.

 

I have my transcoding location set as follows (I have /mnt mapped inside the container)

 

 

 

 

What CPU in in your server? Is it possible that transcoding is too much for your machine and other Apps are suffering? 

 

Could you take a look at htop while watching a video?

[apgood 0]

Thanks. Only just started trying out Emby.

 

That might be the issue. I'll find the setting and change it. See if that fixes it.

 

No CPU is fine it is a Xeon E3 1225 v2.

[hurricanehrndz 149]

It could happen if you have autoupdate turned on. Please use the new testing template https://github.com/MediaBrowser/Emby.Build/tree/master/unraid-templates/Emby

 

Sent from my D6603 using Tapatalk

[hurricanehrndz 149]

Ps you say that emby is using more space yet you say only 9 gigs is being used from the 60 GB you assigned to your docker.img file. I can't see emby using an additional 50 gigs in two days. The only thing that could make the image size grow other than having mount volumes incorrectly setup is a stray log file, but the rate of increase would not be enough to eat an additional 50 GB in two days. Please report back with the volumes you are using and the percentage of use of the docker img file as reported by unraid before starting emby and at various time intervals after starting emby.

 

Sent from my D6603 using Tapatalk

[apgood 0]

Sorry for the late reply I've been busy as we're preparing to relocate overseas.

 

I think this is at moment going to be hard to track down. As the other day I also notice even though unraid reported plenty of free space on my cache drive on the Main page it was in actual fact it had run out of space.

 

What I suspect is happening is that unraid is reporting the actual space used. While the Dockers etc see what space is left based on allocated space (e.g. it seems when downloading files from BitTorrent it creates a file who's size is reported to be what it will be when the file download is complete).

 

Based on that I now don't think it is the docker image running out of space, but rather that the cache is running out of space but it isn't reporting it on Main page of the unraid gui.