Docker container size issue

[hurfi]

There seems to be unmapped paths somewhere here, I've mapped /blackhole, /data & /downloads correctly but the application is writing data to somewhere within the docker image. (can't tell where it is due to not being able to open a shell *another bug?)
I had the docker image blow out to several hundred gig and kill my server.

The only way way to manage it is to limit downloads to a single file at a time because this combined with permissions not working correctly will quickly blow away terabytes of disk space.

I'm guessing it's the download cache, unzip location etc.. can these be mapped to somewhere outside the container please?

Cheers!

[hurfi]

##################################################################################
List of containers showing size and virtual size
##################################################################################

First size is the writable layers of the container (Virtual size is writable and read only layers)

236GB (virtual 236GB) Is being taken up by ......... ghcr.io/jackdallas/premiumizearr:v1.2.7-rc1

[JackDallas]

The only over directory it uses will be the unzip directory which you can set in the settings, it's suppose to keep that clean though. It may be using /tmp for something I've had a look as the source and that could be it, I can't remember that well I'm afraid

... this could be a bug, I'm afraid I can't promise it'll be fixed I'm not using this project anymore so may not have the time