search

mikenye / docker-striparr

Strips metadata from files downloaded by Sonarr and Radarr. Triggered via WebHook.
29 stars 0 forks source link

docker.img filling up #25

Closed HStep20 closed 2 years ago

HStep20 commented 3 years ago

Just had my containers crash because my docker.img filled up. I expect the case is that it was transcoding/remuxing into the .img, and there wasn't enough room left for the large movie file.

Is there a common path that it always transcode at, so I can map it to a volume on an ssd? I did a quick skim of the script, but didn't see anything that stood out path-wise for a transcoding directory.

mikenye commented 2 years ago

It does transcode into the /tmp of the container, then moves the transcoded file over the top of the original file upon success.

Can I trouble you to run docker exec -it striparr find /tmp and post the output (if not sensitive)? That way we can determine if your /tmp is filling up for some reason.

HStep20 commented 2 years ago

Yep, I found it.

My issue was that /tmp was located inside my space limited docker image. Now that I know it transcodes to '/tmp', I've mapped it to a folder outside of the .img, so it doesn't fill up. Thanks!

mikenye commented 2 years ago

I'm glad that's solved your problem. :)