2024-07-26, 08:30 AM
Jellyfin container size
2024-07-26, 09:07 AM
From time to time, you must cleanup in docker
![]() 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
Server: Intel NUC N5105 - 32 GB RAM
HDD: 1 x WD Red SA500 2TB + 2x 8 TB + 2x 4 TB WD Red Plus in 4x LC-35U3-C-HUB OS: Debian 12.9 + Jellyfin 10.10.6 (Docker) | Content up to 2160p + transcoding Network: 2x ASUS Tuf Gaming AX6000 in Aimesh on 1/1 Gbit
2024-07-26, 10:58 AM
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). ![]()
2024-07-26, 04:43 PM
(This post was last modified: 2024-07-26, 04:44 PM by Hectik. Edited 1 time in total.)
(2024-07-26, 10:58 AM)Efficient_Good_5784 Wrote: Do you have trickplays and chapters enabled for any of your libraries? 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:
Jellyfin 10.10.3 [LSIO Docker] | Ubuntu 24.04 LTS | i7-12700T | 16 GB RAM | 60TB Storage
|
|
|