Self-Hosted Version
25.10.0+57
CPU Architecture
aarch64
Docker Version
28.5.1
Docker Compose Version
v2.40.1
Machine Specification
Installation Type
Fresh Installments
Steps to Reproduce
Disk usage should remain under control during normal operation.
Old logs/events should rotate or clean automatically without consuming excessive storage.
Cleanup commands should reduce disk usage properly.\
Expected Result
Disk usage grows very quickly and fills the server storage.
Docker container logs and Sentry data consume large space.
Manual cleanup is required frequently to prevent downtime.
Actual Result
Actual Result
Fresh Installation
Running on AWS EC2
Using Docker Compose installation
Cleanup command used:
docker compose run --rm web sentry cleanup --days 7
Docker logs were also truncated manually:
sudo find /var/lib/docker/containers/ -type f -name "*.log" -exec truncate -s 0 {} ;
Issue still persists.
Disk data.txt
docker disk.txt
docker ps sentry data.txt
Event ID
No response
Self-Hosted Version
25.10.0+57
CPU Architecture
aarch64
Docker Version
28.5.1
Docker Compose Version
v2.40.1
Machine Specification
Installation Type
Fresh Installments
Steps to Reproduce
Disk usage should remain under control during normal operation.
Old logs/events should rotate or clean automatically without consuming excessive storage.
Cleanup commands should reduce disk usage properly.\
Expected Result
Disk usage grows very quickly and fills the server storage.
Docker container logs and Sentry data consume large space.
Manual cleanup is required frequently to prevent downtime.
Actual Result
Actual Result
Fresh Installation
Running on AWS EC2
Using Docker Compose installation
Cleanup command used:
docker compose run --rm web sentry cleanup --days 7
Docker logs were also truncated manually:
sudo find /var/lib/docker/containers/ -type f -name "*.log" -exec truncate -s 0 {} ;
Issue still persists.
Disk data.txt
docker disk.txt
docker ps sentry data.txt
Event ID
No response