July 24, 2025Jul 24 Bringing up an old thread but I'm having this same issue now, did anyone find the culprit? It's definitely something in the plex maintenance tasks. I'm using the plexinc docker. I've been disabling the different checkboxes for tasks trying to figure out which one triggers the docker img growth, no luck so far...
July 25, 2025Jul 25 For me it was mapping tmp and transcode directories in the docker template to an external directory.
July 26, 2025Jul 26 Thanks, that makes sense, I recently added a mapping for /var/tmp -> /mnt/user/appdata/PlexMediaServer/tmp/ so we'll see if that works. I was consistently hitting docker img errors Thursdays at 2am when. my weekly plex tasks run, we'll find out next week if it worked!
September 19, 2025Sep 19 Having the same issue, everything was stable past few years. I'll look into the solutions above. For me the image goes up close to 40Gb. crazy!
November 1, 2025Nov 1 I ran into this same issue. I found another route where plex stores temp files, so I mapped it, too. Here it is for reference. Hope it helps you as it did for me!
December 7, 2025Dec 7 I've had this happening with my unRaid server for quite some time but never knew which docker was responsible, today I stumbled upon it being Plex when I manually invoked "optimize database" command inside Plex.My transcode has already been remapped and I've just remapped tmp but it's still happening (not fixed).
December 12, 2025Dec 12 Leaving this here for any one in the future needing ithttps://github.com/ChuckPa/DBRepairOption 23 is how to shrink the bloated DB. Also recommend running Option 2 after that completes.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.