tmp files can grow out of control and fill the entire drive

[Andrew-T-Smith]

Is there a pinned issue for this?

• I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

• I have searched the existing issues
• I have searched the existing discussions

Is there any comment in the documentation for this?

• I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

• I have checked the provider repo for issues
• My issue is NOT related to a provider

Are you using the latest release?

• I am using the latest release

Have you tried using the dev branch latest?

• I have tried using dev branch

Docker run config used

version: '3.3'
services:
transmission-openvpn:
cap_add:
- NET_ADMIN
volumes:
- /mnt/media/torrents/downloading:/data/incomplete:rw
- /mnt/media/torrents/completed:/data/completed:rw
- /etc/localtime:/etc/localtime:ro
environment:
- OPENVPN_PROVIDER=PIA
- OPENVPN_USERNAME=
- OPENVPN_PASSWORD=
- LOCAL_NETWORK=192.168.1.0/24
- HEALTH_CHECK_HOST=github.com
- PUID=1003
- PGID=1003
- TRANSMISSION_UMASK=18
logging:
driver: json-file
options:
max-size: 10m
ports:
- '9092:9091'
image: haugene/transmission-openvpn
container_name: transmission-openvpn-temp
restart: unless-stopped

Current Behavior

On two separate devices now, (but downloading the same torrent), I have come to find the hard drive filled on the device with a major culprit being this container writing an excessive amount of tmp.XXXXXXXXXX files in the container's tmp directory. Logs seem to have been deleted...

Both of these devices only had this one torrent. Maybe the container should keep an eye on this directory? I am guessing there was something wrong with the torrent somehow, as multiple of these tmp files were created per minute.

(Sorry, I know this issue is absolutely garbage. I do still have the torrent and could maybe do testing later but for now I need to clean this up so my system can run again)

Expected Behavior

Clear the tmp directory if it is growing excessively (dozens and dozens of GB, thousands of files)

How have you tried to solve the problem?

1. I haven't, on both affected systems I had to purge the container to get things running again. This container was low priority. But I am willing to do some testing if you can give me tests to do.

Log output

There are no longer logs for the time when this container was making a ton of tmp files, sorry.

HW/SW Environment

- OS: Debian 13 (and seen on Raspbian 11)
- Docker: Docker version 26.1.5+dfsg1, build a72d7cd

Anything else?

It's been a while, so I can't really give any better info, but this torrent was possibly stuck in the high 90% or so range? Not because of a lack of peers, but for something else (no clue what it was though). Again, I still have the torrent, multiple systems in multiple locations, I WILL test for you if you give me steps you want done.

[spacemanspiff2007]

Could this be be related to a transmission issue?
Transmission 4.0.6 really improved the behavior so updating to the latest version would be very nice.

[ilike2burnthing]

As per the issue template, try the dev branch.