Redis db backup volumes piling up...pruning required?

Gramps Web
1

This is meant to be a continuation of this thread - please merge: Missing Redis volume Using docker-compose.yml from documentation

After starting and stopping my GrampsWeb server (based on the Let’s Encrypt example) several times, I noticed I have many volumes piling up with dump.rdb (a Redis DB backup) in them:

❯ docker volume list
DRIVER    VOLUME NAME
local     7e63c1564f88dc5174b0afd3006241f5e4557943e39f1dca5d8a2099ee3b3073
local     8b799fb920bbae232270649d2a3f9458c3e548aed991392368deb4aa866d0ff3
local     56ef730c4b637a3cb55c538a05c47d6faaead572ad79325f34e031a83e64fcfd
...

Should I be pruning these volumes manually? Will lose anything if I delete the 12 volumes I currently have?

It seems like configuring a persistent volume as suggested by @tonic8 is the way to go to avoid these “anonymous” volumes from being created with each start? Thanks.

2

Will lose anything if I delete the 12 volumes I currently have?

No.

It seems like configuring a persistent volume as suggested by @tonic8 is the way to go to avoid these “anonymous” volumes from being created with each start? Thanks.

Probably. It’s really a question about redis or docker compose.