duplicacy settings don't stick about docker-duplicacy HOT 5 OPEN

The only thing I can think of, and one which might simplify everything, is to get rid of the /etc/duplicacy bind mount and all the linking stuff. Instead, just bind mount in the entire ~/.duplicacy-web folder.

from docker-duplicacy.

what's the rationale behind the bind mount and links anyway? What are we losing by removing that?

from docker-duplicacy.

I assume it's the same error:

I just moved servers and copied the relevant parts of docker-compose.yml as the local directories mapped to these volumes:

/var/cache/duplicacy
/etc/duplicacy

after starting the container I was asked for the password. the strange thing is, that the files in /etc/duplicacy on the local drive are re-created if deleted, so, duplicacy seems to use the volumes from the config.

any short term workaround to copy over the configs?

from docker-duplicacy.

Hi everyone. I have my settings file persisting based on reading some of the comments here and in the other issues by doing the following.

1. Leave the volume mounts relating to /etc/duplicacy as per Eric's original compose file;
2. Add the following volume mount:

volumes:

• /[your hostlocation]:/home/.duplicacy-web

This seems to work for me through multiple reboots, shutdowns etc. I do not loose all my schedules.

@ Eric - any chance you might be able to update the docker image to the latest version of the web gui? Thanks a lot

from docker-duplicacy.

As an update, my settings had survived multiple reboots, container shutdowns etc and the settings persisted with the above configuration. However, recently I needed to move my reverse proxy to traefik and in testing I shutdown the container a number of times and from the command line. I lost my settings. I tested though and when I shutdown the container by stop and restarted with start from the container gui provided by Cockpit, the settings persisted. I don't know why shutting down the container via the command line versus a gui causes this issue. I managed to get Traefik to reverse proxy to the default http port with Letsencrypt certificates working so my login is now protected by https encryption. Happy to share some settings of how I did this in Docker.

from docker-duplicacy.