feat: Allow customization of CLI docker command that spawns task container #1779
Description
Is your feature request related to a problem? Please describe.
[self-hosted]
My main use case for Trigger.dev is to download large files (5Gb-50Gb) and to perform heavy processing on them automatically. Once they are processed, I want them to stay stored in a local folder that will persist. I don't want to upload them to S3 or anything else. I have 10TB bare-metal servers (100$/mo, lot cheaper than S3) that have trigger.dev installed on them, so the idea is really that it's downloaded once and then I don't have to pay the network / storage cost again.
My only issue right now is I'm not able to bind /my_persistent_data:/anywhere_in_task_docker. I've asked on the Discord community and it seems to be no way around this.
Describe the solution you'd like to see
To allow us to alter the way the task container are spawn, or even better to allow a docker-compose setting to list folders that need to be bound.
Describe alternate solutions
The solutions proposed in the Discord are to setup a localhost S3 server, I spent 3 hours trying to do this and it's far from simple, especially if you want it to fit in a docker-compose. I tried to setup a localhost FTP server until I realised both options wouldn't work anyway as I can't create a docker network between these services and the task container you spawn.
Additional information
No response