Downloading media from Emby quickly fills up the unRAID docker image

[seanbuff 1315]

15 hours ago, ryzen5000 said:

How can I mount to cache when my media files are not on cache? When I map to mnt/user I can access any path and any share I need for media files. I don't understand how mapping to cache will let me access my media.

I'm not talking about media files, just the Emby app data. I was only referring to cache because you said it was mapped to a share on the cache drive.

Presumably you have your Emby media stored in the array which would be on something like: /mnt/user/Movies

but the Emby appdata is unlikely to be on the array, so should remain on cache - which would be /mnt/cache/appdata/emby

Hope that makes more sense

[Lessaj 467]

In the video you posted, was that on the same local network as the server? Because outbound rarely went much above 100 Mbps which seems odd if it's local, and the speed doesn't stay there either it keeps dropping down to basically 0 (just a few KB).

[artichoke 1]

This is happening to me too. My transcoding paths are all set to a different SSD, not that it matters. Someone is downloading something right now and it's not transcoding, but it is filling up my docker image until the transfer is done

 

Edit: I turned on debug logging and it don't see anything about downloading unfortunately

Edited October 2, 2024 by artichoke

[ryzen5000 17]

I never found a solution why the docker is filling up during downloading from Emby even though it's not transcoding and it's mapped to a ssd. Emby is even installed on it's very own ssd. Any way to fix this? Mabye it's not a problem I can fix myself it needs to be done through an update. 

[Luke 42077]

On 10/2/2024 at 2:15 PM, ryzen5000 said:

I never found a solution why the docker is filling up during downloading from Emby even though it's not transcoding and it's mapped to a ssd. Emby is even installed on it's very own ssd. Any way to fix this? Mabye it's not a problem I can fix myself it needs to be done through an update. 

HI there, what folders are taking up the most space?

[artichoke 1]

I tried reproducing the issue, mounting my docker.img file, and inspecting the contents for a large folder/file but I couldn't find anything. Not 100% sure I did it right though

[ryzen5000 17]

Hi, If you check back to my post on September 10th you will see that I am running Emby in a docker on Unraid. I am not sure what you mean Luke about folders. There was the option to have docker compiled in a folder structure however that would have to have been done from day 1. Default is having a docker.img. As the diagram I drew with the red arrow shows, docker image on my Unraid dashboard fills up almost entirely while downloading. I will also mention that the people downloading combined were often 15 plus movies and some series all at the same time. There is no way to restrict the amount of downloads my clients press at once and they are overloading the docker.img and the only solution I have found is to disable downloading. Although I had some unhappy campers who like to download for offline watching I noticed that they were downloading excessively for few hours at a time one after another up to 20 movies at once. I don't know if Emby is cut out to handle this much downloading while its inside a docker image? They want to download from Emby like they would a torrent app, multiple files at once and full series.

Edited October 4, 2024 by ryzen5000

[seanbuff 1315]

As previously stated, the typical cause of docker.img filling up is due to an application writing to a path that hasn't been mapped. Check the settings within each application and make sure any path specified within the application is a container path mapped to a host path.

As a temporary solution, have you tried expanding the Docker image size? UnRAID FAQ: How do I increase the size of my docker.img file?

Also a helpful video for more information:

 

[artichoke 1]

I've checked all the paths in both the unraid UI (it's just /mnt), and in the emby UI. In the UI, it's cache and transcoding paths that can be set. It's possible a new path got added that isn't reflected in the unraid docker template. This was not an issue a month or so a go, so I think it's unlikely to be a typical path that is unmapped. Looking here, there's not much to be mapped anyway: https://hub.docker.com/r/emby/embyserver

Regarding resizing, my docker image is 50gb, and only 26gb is typically used. So when someone is downloading a few things at a time, it's using 24gb of ... something. Resizing it might work, or it might just let it use even more haha.

[Neminem 1518]

Next time check this option in your unraid docker page.

It will show what docker is filling up.

[Neminem 1518]

Here are some other commands to run if you docker.img is filling up on unraid.

If you run docker image ls from a terminal on the server, you'll get a list of all images that are being stored including their size.

If you run docker system df , that'll provide a summary showing total size of images, containers, volumes, build caches, etc.