how to prune docker NXfilter?

[magnusemail]

hello team,

Please may I ask how to prune NXfilter when running it as a docker compose instance ? My compose file is as below and works well, however the docker container continues to grow and and is fast approaching exhausting disc capacity as an ever growing Overlay file.

Is there a way to rm or archive within the container? Is there any way to set a limit and over write ?

Stopping and restarting docker does not help, and the logging limit in the compose file appears to work for the volumes outside docker, but it does not stop the growth within the container?

Grateful for any help or tips.

many thanks
Magnus

**************************************************
Running compose file
version: "3.9"
x-logging:
&default-logging
options:
max-size: '128m'
max-file: '7'
driver: json-file

services:
nxfilter:
logging: *default-logging
image: packetworks/nxfilter-base:latest
container_name: nxfilter
restart: unless-stopped
ports:
- "80:80"
- "443:443"
- "53:53/udp"
- "19002-19004:19002-19004"
volumes:
- nxfilter-conf:/nxfilter/conf
- nxfilter-log:/nxfilter/log
- nxfilter-db:/nxfilter/db
volumes:
nxfilter-conf:
nxfilter-log:
nxfilter-db:
************************************************** *****

Disc show files as
root@nxfilter1:~/nxfilter# df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 796M 1.4M 795M 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 23G 18G 4.0G 82% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/loop2 68M 68M 0 100% /snap/lxd/21835
/dev/loop4 54M 54M 0 100% /snap/snapd/18933
/dev/sda2 1.5G 209M 1.2G 16% /boot
/dev/loop3 92M 92M 0 100% /snap/lxd/24061
/dev/loop5 54M 54M 0 100% /snap/snapd/19122
/dev/loop6 64M 64M 0 100% /snap/core20/1879
/dev/loop0 64M 64M 0 100% /snap/core20/1891
tmpfs 796M 0 796M 0% /run/user/1000
overlay 23G 18G 4.0G 82% /var/lib/docker/overlay2/7dfe9414f132c92b90abd1a10a61fb4ccfd81064be8d1181b2 24c239e29348f7/merged

************************************************** ***********

[magnusemail]

Update - the growth appears to be the file "traffic.h2.db"

Is it safe to stop docker and delete this file and then restart NXfilter ?

Is there any way to set a limit so that this file on reaching the limit starts re-writing ?

thanks

[support200]

You can stop and delete the file and restart it if you don't need traffic data. It will recreate it.

You also can set limit on 'System > Setup > Misc > Log Retionsion Days'. You may need to run /nxfilter/bin/dbclean.sh' overnight while you stop NxFilter as it might not use the empty space in the db before you clean up.

If you export log data using Syslog then you may set 'Log Retionsion Days' to 0. It still keep some data in its traffic db but not DNS request log.