YH

Any updates on this issue? As long as `--domains` option can take only one value at a time, it is cumbersome to configure some bash scripting to generate domains. Since...

> @YuryHrytsuk Have you tried to limit the memory using https://phoenixnap.com/kb/docker-memory-and-cpu-limit This will kill the container (exit_code 137). Since the memory consumption jumps at around 11:00 PM (i.e. during the...

> How big are your database dumps, Maybe you could manually execute the container and run the following > > ``` > free -m > /backups.sh > free -m >...

I executed the `free` command again in ~30 mins just in case ```bash $free -mh total used free shared buff/cache available Mem: 31Gi 12Gi 1.6Gi 257Mi 17Gi 18Gi Swap: 0B...

Well, I apologize but the output of `free` command apparently does not make sense since it shows memory of the whole machine. However, Prometheus `container_memory_usage_bytes` metric still points to memory...

@NyakudyaA any updates on this matter?

My bad. Our backups indeed caused the memory increase

> You should be able to check the cron logs https://github.com/kartoza/docker-pg-backup/blob/master/build_data/backups-cron#L2C47-L2C63 Is it possible show these logs in container's logs?

> Or just add your own custom cron file with that logic > > ``` > -v ./backups-cron:/settings/backups-cron > ``` It looks like this file will never be used because...

> > Or just add your own custom cron file with that logic > > ``` > > -v ./backups-cron:/settings/backups-cron > > ``` > > It looks like this file...