Jellyfin Forum
Jellyfin container size - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin container size (/t-jellyfin-container-size)



Jellyfin container size - Niels Voogd - 2024-07-26

Hey All,

For a couple of months i've been trying to resolve an issue with my jellyfin container size on an unraid server. It keeps growing and growing. I've already used the scheduled task to remove my cache, but that doesn't seem to solve it. Where else could i look on my server?

[Image: ihvidOMETDaukEosRNlbGsiw?allow_redirect=true]
[Image: pekRUmeQQZkHuuNNLbZSnxLX?allow_redirect=true]

Thanks.


RE: Jellyfin container size - 34626 - 2024-07-26

From time to time, you must cleanup in docker Smiling-face

Be aware, it's your own responsibility to backup your data!

You can use this docker command to cleanup - It will tell you whats going to happen before you accept it:
sudo docker system prune


RE: Jellyfin container size - Efficient_Good_5784 - 2024-07-26

Do you have trickplays and chapters enabled for any of your libraries?

After v10.9, trickplays are generated in Jellyfin's config folder, which most likely is in the Docker container (unless you pulled it out and stored it somewhere on the NAS).


RE: Jellyfin container size - Hectik - 2024-07-26

(2024-07-26, 10:58 AM)Efficient_Good_5784 Wrote: Do you have trickplays and chapters enabled for any of your libraries?

After v10.9, trickplays are generated in Jellyfin's config folder, which most likely is in the Docker container (unless you pulled it out and stored it somewhere on the NAS).

He's right! It was an anoying change they did with trickplay as the folder just became too big to handle and sort of messed up my backup solution. My metadata folder is at 100GB at the momment.

You can double check by running the following command in whatever directory your jellyfin config folder is.
Code:
du -sh ./config/data/metadata/


One workaround you could do is to copy the metadata to your media drives and then map the folder as a volume in your docker-compose.yml like below:
Code:
volume:
  - /<different directory>/metadata:/config/data/metdata