Is it just me or or does the offical Docker container seem to be ignoring my container settings folder (/mnt/user/appdata/duplicati/) and instead using a goofy folder like "/var/lib/docker/volumes/xxxxxxx/_data/Duplicati/"?
I found a few different versions (container updates?) using find /var/lib/docker/volumes -name "Duplicati-server.sqlite".
For those that might stumble on this, I’ve found that when my official Docker container changes the appdata folder (even if just updating a Docker setting) it loses all my settings (jobs, global settings, etc.)
I recover from this by:
making sure the “empty” Duplicati is updated to the same version as the “lost” one (else I risk database version errors)
searching /var/lib/docker/volumes for Duplicati-server.*
stopping the Duplicati Docker
copying the contents of the folder with the SECOND newest Duplicat-server.sqlite file into the NEWEST folder (overwriting an contents)
starting the Duplicati Docker
confirming my jobs and settings are back
Again, I don’t know if it’s just me having this issue or not, and I assume there’s a better way to recover - but for now this is working.
The linxuserver/duplicati Docker container stores config at a /config mapping while the duplicati/duplicati Docker container uses /data (and automatically adds Duplicati - or perhaps container name to that).
Unsolved because I just updated to 220.127.116.11 experimental and wanted to test downgrading back to 18.104.22.168 and realized the updates folder specified by my /data container mount point does NOT contain the update folder!
In fact, the only place I’m finding it is INSIDE the Docker in /usr/share/Duplicati/updates so obviously I’ve still got something configured wrongly.