Ah - OK - I was using the linuxserver one for the docker-based installs.
That said, I’ve looked into commiting changes and so it looks doable.
Their example standard usage is:
-e PGID= -e PUID=
where it appears the /config map is where the backup configs are stored, /backups appears to be a mapped drive path for destination if using “local” storage, and /source (you can easily map more than one) how the docker image gets access to the directory/directories being backed up.
• -p 8200 - the port(s)
• -v /config - path for duplicati config files
• -v /backups - path to store local backups
• -v /source - path to source for files to backup
• -e PGID for GroupID - see below for explanation
• -e PUID for UserID - see below for explanation
Turns out at least on synologies, you don’t have to specify the port if specifying the host network.
It’s running 126.96.36.199 right now so I can either download yours and remap the drive paths, wait for them to update and initiate the same command I already use, or run the updater under 188.8.131.52 and commit it as a new version (which may give me a fallback), since the config files should all stay the same, so that I don’t have to wait.
Thank you for the updates.