Sergio

why not this? ```dockerfile ENV MAX_EXECUTION_TIME 600 ENV MEMORY_LIMIT 512M ENV UPLOAD_LIMIT 2048K ENV TZ UTC # $PHP_INI_DIR/conf.d/opcache-recommended.ini; \ \ { \ echo 'session.cookie_httponly=1'; \ echo 'session.use_strict_mode=1'; \ } >...

same on debian and `v2.6` retention was set to `60` days and was working fine, but now seems to be 6 months the growth seems to coincide with `v2.4` release...

@jeffreyssmith2nd the original install and config were done with `v2.0` (or maybe `v2.1`), the further upgrades were done regularly without changes to the config the downgrade was: `v2.6` > `v2.3`...

It's the partition where `bolt-path` and `engine-path` live and represent 95%+ of the occupied space. I checked the logs, they go back to October 23rd 2022 (so after upgrading from...

I also tried restarting prior to downgrading, but since it takes a while to start deleting shards, maybe I didn't give it enough time... For now I upgraded back to...

looks like deletion still takes place after upgrading `2.3` to `2.6.1` ``` ... ts=2023-01-11T00:14:21.006813Z lvl=info msg="Deleted shard group" service=retention op_name=retention_delete_check ... ```

This could be as simple as a `SEMAPHORE_(TERRAFORM|TOFU)_VERSION` env var, which, if exists, is acted upon in `server-wrapper` on boot. And for minimum effort you could bundle a dummy script...