Docker image size balloon

Hi,

may anyone has an idea why the docker is ballooning so much, i guess its the EPG in some way …

when i remove DVR and readd docker size is back to normal ( ~ 400 - 500 mb), after a little while its
up to 7 gb …

can anyone tell me where Plex is storing its EPG datas (artworks etc …) ?

thanks ahead.

Server Version#: latest
Player Version#:

Not sure this is related to EPG. Plex can be quite heavy on caching and storing e.g. local media assets which easily add up to several GB of data („several“ as in way beyond 7 GB :wink: ).

You can use this support article to identify / locate the related folders:

Thanks for the Tip, that i already checked and thats a docker mounted drive, all good here.

its just significant that when i redo a DVR setup the docker size is ok, with each day it increases … i have plenty of Media already and since a while (my Plex Server is running for almost 2 years pretty untouched) the docker size increasing is pretty high, never had a real look at it but since my unraid server warned about docker disk … i took a closer look, and plex is incredible growing after DVR renewal (thats something i did quite often in the past for testing tuners).

i think i found it, the /tmp folder has 3.2 GB here after a few days

du -sh /tmp

3.2G /tmp

cd /tmp

ls -la

total 3282792
drwxrwxrwt 1 root root 4266 Oct 23 20:04 .
drwxr-xr-x 1 root root 390 Oct 17 04:14 …
-rw-r–r-- 1 plex users 37352778 Oct 19 10:50 0145-dadb-4dc6-c197.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 20:04 0398-1790-ca78-821f.xml
-rw-r–r-- 1 plex users 37311431 Oct 18 03:44 04a2-2a79-4804-eb08.xml
-rw-r–r-- 1 plex users 37352778 Oct 20 03:33 0eef-ba2d-03a7-53e1.xml
-rw-r–r-- 1 plex users 37437386 Oct 22 02:35 14c2-a84f-5c25-e836.xml
-rw-r–r-- 1 plex users 37360250 Oct 17 04:14 1728-b2e1-3ba4-6dbd.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 11:44 1a20-ac52-b7dc-8aed.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 07:33 1a59-5fa6-4ac2-fbc9.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 11:33 1bc8-03f0-3bd4-a7f9.xml
-rw-r–r-- 1 plex users 37352778 Oct 20 02:50 1d4c-4d4c-6fc6-0e9a.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 12:53 2143-fae5-d5ac-852c.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 10:35 22e1-a074-017b-6a07.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 18:15 27a9-1188-de2d-4ece.xml
-rw-r–r-- 1 plex users 37437386 Oct 22 02:35 28fe-7301-af90-42b4.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 22:15 2c7b-a7cf-f804-7f1f.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 08:53 2d47-6811-2f48-88b8.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 15:33 2e13-b710-62ce-efc0.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 16:04 3049-ff69-38dd-03d4.xml
-rw-r–r-- 1 plex users 37157985 Oct 21 06:46 3249-fc0e-b18b-32fd.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 18:50 3a1c-fa7d-08ca-e9a8.xml
-rw-r–r-- 1 plex users 37408689 Oct 23 02:35 3dba-67ea-110b-65a0.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 07:33 423b-aa2a-58e1-7553.xml
-rw-r–r-- 1 plex users 37352778 Oct 20 03:33 43c4-c876-bf4f-fa43.xml
-rw-r–r-- 1 plex users 37437386 Oct 22 02:15 46b5-60e6-baa6-bd55.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 06:50 4860-f575-e539-24fe.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 07:44 4d1d-2cf5-e4d9-c8d6.xml
-rw-r–r-- 1 plex users 37360250 Oct 17 04:53 4fa6-d9b8-1acf-9a1a.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 14:50 5071-a2b0-df5e-f921.xml
-rw-r–r-- 1 plex users 37311431 Oct 18 00:53 524e-d8b3-3fda-e609.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 22:35 535b-1056-d8c4-c20c.xml
-rw-r–r-- 1 plex users 37271918 Oct 19 02:50 5b3c-b26a-8138-596d.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 19:33 5d08-7537-ceb0-141d.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 23:33 61e9-1214-dd68-7508.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 20:04 625c-8350-a69e-3ab8.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 07:44 6387-9328-ef2e-ba0f.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 08:53 6a60-3e9d-aba9-5a95.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 23:44 6c83-624a-3a79-0c7d.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 06:35 6ded-3d9d-741c-06ec.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 06:35 6e67-decf-bd78-ad38.xml
-rw-r–r-- 1 plex users 0 Oct 21 09:56 72ad-bf4f-ffd2-2806.xml
-rw-r–r-- 1 plex users 37309858 Oct 21 02:46 7634-0ed0-aace-91b5.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 15:44 7aee-1e22-8f12-3aac.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 14:35 81b6-29dc-a370-4b30.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 10:15 8263-ea4f-6ae7-6121.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 22:50 84f4-5acb-1fb1-516c.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 20:53 86cd-c6de-1f6c-7d89.xml
-rw-r–r-- 1 plex users 37408689 Oct 23 04:46 8df8-75c8-6af7-7bc6.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 18:35 9590-7f6d-59bb-652f.xml
-rw-r–r-- 1 plex users 37271918 Oct 19 02:50 9692-d5d0-72c2-83cd.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 23:44 9976-84e3-b97c-56ca.xml
-rw-r–r-- 1 plex users 37309858 Oct 21 02:46 9b54-0b1f-d3fa-f3e7.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 18:35 9eb3-a5f7-9127-142e.xml
-rw-r–r-- 1 plex users 37311431 Oct 18 03:44 a03b-325d-e211-36b7.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 12:04 a3f6-009f-e932-da22.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 15:33 a62e-df94-56bc-4e62.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 11:33 a804-574f-eddc-72ca.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 10:15 ab7f-adff-d1ae-91d9.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 08:04 b1ad-d60e-7e8a-17b1.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 12:53 b2ac-376c-3197-9ddc.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 14:15 b9e1-9b13-a4cf-17e5.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 19:44 ba56-33ae-a55e-264d.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 19:44 bb8c-3bf9-1c71-eb0f.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 14:35 bca9-9e43-6633-cb54.xml
-rw-r–r-- 1 plex users 37157985 Oct 21 06:46 be04-c9bc-950e-37dc.xml
-rw-r–r-- 1 plex users 37360250 Oct 17 04:53 bf63-951a-4df1-ff5b.xml
-rw-r–r-- 1 plex users 37311431 Oct 18 00:53 c0ab-a0ce-9bc7-6de2.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 15:44 c115-9956-5eef-11c4.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 20:53 c2df-ecce-4b97-e013.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 22:15 cc40-b11b-6bbc-b23e.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 10:35 ccb3-c71e-ae3e-9ff8.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 22:50 cd54-3f00-681d-5404.xml
-rw-r–r-- 1 plex users 37408689 Oct 22 22:35 cf77-ee8a-83bb-8495.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 14:50 d180-b54f-5237-8dc3.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 19:33 d1a8-cff9-6e2b-ccb4.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 10:50 d3b2-6ba3-55a5-f78b.xml
-rw-r–r-- 1 plex users 37437386 Oct 22 02:15 d41f-6990-0cea-4827.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 16:53 d4f7-e0b4-3bec-f4a2.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 06:50 d5b6-498e-fe22-647c.xml
-rw-r–r-- 1 plex users 37408689 Oct 23 04:46 d746-1c74-cbb1-2118.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 08:04 dc1d-3715-0441-f3b8.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 16:04 df61-a332-396d-9cc1.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 18:15 e399-bae3-4703-df02.xml
-rw-r–r-- 1 plex users 37352778 Oct 20 02:50 e46e-dd1d-501e-ced7.xml
-rw-r–r-- 1 plex users 37311431 Oct 17 16:53 e620-1eb2-11c7-13df.xml
-rw-r–r-- 1 plex users 37437386 Oct 21 14:15 e730-16b0-4bc2-4bfe.xml
-rw-r–r-- 1 plex users 37360250 Oct 17 04:14 ed34-f01a-93ca-39b1.xml
-rw-r–r-- 1 plex users 37408689 Oct 23 02:35 f58b-af04-1b3e-dbf6.xml
-rw-r–r-- 1 plex users 37309858 Oct 20 23:33 f750-ef5b-44b7-9aef.xml
-rw-r–r-- 1 plex users 37271918 Oct 18 11:44 f827-7577-f02d-b2f1.xml
-rw-r–r-- 1 plex users 37352778 Oct 19 18:50 fe61-bd47-af03-cbaf.xml
-rw-r–r-- 1 plex users 37383189 Oct 23 12:04 fe92-d204-4bbf-72e5.xml
drwxr-xr-x 1 plex users 0 Oct 23 08:04 pms-a9398bdd-da4c-4f05-8d2e-b14afe5db014

i ll mount this external too and see what that is.

thanks for the Tipp

so, after a few hours i see there are already some xml files, all are epg xml´s …

may just an idea, it creates all these epg´s for every tuner there was in the past ?

as i mentioned i made some testings with some proxy tuners and never completely reinstalled plex or so cause its all good.

ok, i guess i can confirm what i described, its the amount of epg files created by PLEX,
would be nice to know if these get cleaned automatically or kept “forever”.

Even better, why there are so many epg files created … not even 2 days almost 1 GB :wink:

Well it’s /tmp, so it should get cleaned after rebooting. Dunno how this is handled in a docker though…

Can you send me one or two of the files? We’ll write out json if parsing data during an EPG refresh fails, but I can’t think of anything else that we’d write out at that size.

i guess (and hope) so, but i dont reboot my server too often regular :wink:

so my “personal” opinion would be to clear them if not needed anymore …

of course, each file has ~ 35+ mb, howto send ? email, dl link in pm ?

its the epg.xml files u download from my epg source

sample from xml entrys



just leave a note howto send you the files

You could restart the docker and/or server to see if the files disappear. But first save them for timwoj :wink:

No need to send the files. I just needed to know what they were exactly. We do save off the XMLTV data in the PMS HTTP cache, and they’re saved there with different names. I’ll have to dig into why those are getting saved into temp.

ok, and may also what its about those double savings …while you on it anyways, as the timestamps tell they are always double loaded and saved …

i only have 1 DVR configured, i had some weeks ago 2 configured when i thought about a backup solution, but as this aint working anyway i removed the 2nd DVR, but i removed them completely …
in case u need infos about “old” DVR´s, entrys from media provider ressources in the buttom …
may when i see there are 2 entrys in data <?xml version … where those 2 epg downloads come from …
and as there is no real “cleanup” function in plex about unused tuners … just trying to get it sorted.
Rest is working wonderful meanwhile since i figured my playback and recording errors i had, fixed by stripping dvb subs and teletext from my streams (i use DVB through TVHeadend as note).

i hope these infos help maybe.

image
image

@timwoj may a quesion between

could u tell me where to look for why there are always 2 loaded epg´s like there where 2 sources ?

1 actually only use 1 virtual tuner and 1 epg source (cant use more anyway in plex)

sample, just wiped all xml files and did a guide refresh in plex

same file with 2 different names, same content on both files

solving this would at least half the size :wink:

thanks ahead for an tip


Ah, I think I see the bug now in the XMLTV parser. If it’s an absolute URL (like you’re downloading it remotely from the web), we save it to a temp file before parsing. Apparently that never gets cleaned up. The reason I wasn’t seeing it in my testing is that all of my XMLTV data is on the local disk and it doesn’t do that download. I’ll open an issue and get it fixed up. Thanks for the excellent bug reporting!

perfect, thanks for the info :wink:

i can also change to file, but i wait for the update :wink:

may still an idea about the “double” loading ?

It’s because of the way we load the XMLTV data when refreshing the guide. We load the XMLTV file once to load/verify the channel mapping, then load it a second time when loading the actual airings. There’s no cache in between those loads, so it downloads the URL twice to separate files. I’ll fix that while I’m fixing the rest.

perfect, then i understand it :wink: already thought has something todo with “old” PVR Tuners :wink:

thanks alot

@timwoj may an update on this issue … still same behavior as note.

@alturismo I fixed it and committed a change for it, but it didn’t make the cut for 1.14.x. It will for sure be in 1.15.0.

thanks for the info