bug: rEngine not properly purging data

[offseq]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When deleting all of the data by rEngine as per https://rengine.wiki/usage/settings/, and also manually deleting scan history, the disk usage still remains high.

root@null~ # df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           6.3G  2.1M  6.3G   1% /run
/dev/md2        436G  412G  2.1G 100% /
tmpfs            32G     0   32G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/md1        989M  245M  693M  27% /boot
/dev/nvme1n1p1  256M  316K  256M   1% /boot/efi
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/2b8251db92a19c7bfb96525663c69d34dd4ca0f2b2da81b96b2b462e13ec3d0e/merged
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/c7627e805ae37d2fecf5e897f0d58d3b876ba4c1d5b17f07ebc3b83021058ad0/merged
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/4c1390c83d60be3c50f37d118e13a59f1301a306a9bfb42effc35b092b51601c/merged
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/c27f4f2798477c5268861f7eb69a8f9b26b87b347453d7a6812fe02aef67ebe5/merged
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/6111fb51e00999358e6fe1061f4c04de70552ec52c169a31f4505a5e2dbe5ed0/merged
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/c3e93581dff887cae02fffe400c2a3941f128320ffd0c35794846f9aebc33e6c/merged
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/6a1380e18803c4e61ec90d2862885aa64be35b63049cc3c0cc27b85bfb7bca9f/merged
overlay         436G  412G  2.1G 100% /var/lib/docker/overlay2/d28580f8923aef84768134c4c36c9682ae49ed5316c03e43b49ea63f90372429/merged
tmpfs           6.3G     0  6.3G   0% /run/user/0

This is after the instance was restarted. docker system prune -a -f does not help cleaning much more.

Expected Behavior

root@null /var/lib/docker/volumes # pwd
/var/lib/docker/volumes
root@null /var/lib/docker/volumes # du -sh
394G	.

root@null /var/lib/docker/volumes # find . -type f -exec du -h {} + | sort -rh | head -n 50
1.1G	./rengine_postgres_data/_data/base/16384/17538.4
1.1G	./rengine_postgres_data/_data/base/16384/17538.3
1.1G	./rengine_postgres_data/_data/base/16384/17538.2
1.1G	./rengine_postgres_data/_data/base/16384/17538.1
1.1G	./rengine_postgres_data/_data/base/16384/17538
1.1G	./rengine_postgres_data/_data/base/16384/17536.99
1.1G	./rengine_postgres_data/_data/base/16384/17536.98
1.1G	./rengine_postgres_data/_data/base/16384/17536.97
1.1G	./rengine_postgres_data/_data/base/16384/17536.96
1.1G	./rengine_postgres_data/_data/base/16384/17536.95
1.1G	./rengine_postgres_data/_data/base/16384/17536.94
1.1G	./rengine_postgres_data/_data/base/16384/17536.93
1.1G	./rengine_postgres_data/_data/base/16384/17536.92
1.1G	./rengine_postgres_data/_data/base/16384/17536.91
1.1G	./rengine_postgres_data/_data/base/16384/17536.90
1.1G	./rengine_postgres_data/_data/base/16384/17536.9
1.1G	./rengine_postgres_data/_data/base/16384/17536.89
1.1G	./rengine_postgres_data/_data/base/16384/17536.88
1.1G	./rengine_postgres_data/_data/base/16384/17536.87
1.1G	./rengine_postgres_data/_data/base/16384/17536.86
1.1G	./rengine_postgres_data/_data/base/16384/17536.85
1.1G	./rengine_postgres_data/_data/base/16384/17536.84
1.1G	./rengine_postgres_data/_data/base/16384/17536.83
1.1G	./rengine_postgres_data/_data/base/16384/17536.82
1.1G	./rengine_postgres_data/_data/base/16384/17536.81
1.1G	./rengine_postgres_data/_data/base/16384/17536.80
1.1G	./rengine_postgres_data/_data/base/16384/17536.8
1.1G	./rengine_postgres_data/_data/base/16384/17536.79
1.1G	./rengine_postgres_data/_data/base/16384/17536.78
1.1G	./rengine_postgres_data/_data/base/16384/17536.77
1.1G	./rengine_postgres_data/_data/base/16384/17536.76
1.1G	./rengine_postgres_data/_data/base/16384/17536.75
1.1G	./rengine_postgres_data/_data/base/16384/17536.74
1.1G	./rengine_postgres_data/_data/base/16384/17536.73
1.1G	./rengine_postgres_data/_data/base/16384/17536.72
1.1G	./rengine_postgres_data/_data/base/16384/17536.71
1.1G	./rengine_postgres_data/_data/base/16384/17536.70
1.1G	./rengine_postgres_data/_data/base/16384/17536.7
1.1G	./rengine_postgres_data/_data/base/16384/17536.69
1.1G	./rengine_postgres_data/_data/base/16384/17536.68
1.1G	./rengine_postgres_data/_data/base/16384/17536.67
1.1G	./rengine_postgres_data/_data/base/16384/17536.66
1.1G	./rengine_postgres_data/_data/base/16384/17536.65
1.1G	./rengine_postgres_data/_data/base/16384/17536.64
1.1G	./rengine_postgres_data/_data/base/16384/17536.63
1.1G	./rengine_postgres_data/_data/base/16384/17536.62
1.1G	./rengine_postgres_data/_data/base/16384/17536.61
1.1G	./rengine_postgres_data/_data/base/16384/17536.60
1.1G	./rengine_postgres_data/_data/base/16384/17536.6
1.1G	./rengine_postgres_data/_data/base/16384/17536.59

It seems that Postgres data are not properly purged, which actually should.

Steps To Reproduce

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.5 LTS
Release:	22.04
Codename:	jammy

vanilla set up with rEngine

Environment

- reNgine: 2.2.0
- OS: Ubuntu 22.04.5 LTS
- Python: 3.10.12
- Docker Engine: version 27.3.1, build ce12230
- Docker Compose: version 1.29.2, build unknown
- Browser: N/A

Anything else?

No response