Hey @Piotr,
Just jumping in for Finnian as he is currently off shift as part of our Australian based team.
Just to let you know, Worker package retention runs periodically and is a system task on the machine not a task performed by Octopus as part of a retention policy.
There is a forum post here which explains how it works so I would take a look at that as I popped some log snippets in there too about what you can see and how it removes the packages from a worker.
At the moment the only way to remove bulk packages from a worker would be to run a script to remove any files over x days old in the worker folder, you will need to account for each worker instance you have on that machine. And then run that script either through Octopus as a runbook, or possibly have Windows run it from the Task Scheduler so it runs every so many hours or on start up.
Having SSH workers or tentacle ones wont make a difference I am afraid so the script option would be the only one at the moment.
Let me know if you have any questions surrounding this at all as I would be happy to help.
Whilst I know that does not solve the issue of the container files filling up the drive I thought I would update you on how the package retention worked on workers. The removal of the files does get done on:
C:\Octopus\[Nameofworker]\Files\ (if on a windows machine)
So it does not affect the work folder you mentioned but hopefully that alleviates any concerns you had with the previous issue you mentioned about package retention not running on workers.
Kind Regards,
Clare