Bug: /etc/duplicacy does not contain updated settings

[Nite16]

I created a Duplicacy container, changed some settings, then inspected my duplicacy.json file in /etc/duplicacy and it is still blank. Restarted the container multiple times, and while my config is retained on the web UI it is not reflected in /etc/duplicacy.

I opened a terminal into the container and I am seeing the correct settings stored in ~/.duplicacy-web/duplicacy.json.

[Nite16]

Appears to be related to the other issue. But the settings are retained in the duplicacy-web folder.

Running readlink on the etc files shows no symlinks, so the symlinks are being broken. This means when re-creating the container, all settings are lost.

[jtfidje]

Did you find a solution to this?

[Nite16]

For now, until this is resolved, I ended up going with the saspus-duplicacy-web container.

[scott-ainsworth]

This is really an interaction between this container and Duplicacy. On startup, the Dockerfile symlinks from /root/.duplicacy-web/duplicacy.json to /etc/duplicacy/duplicacy.json. This should work (and I believe used to work). The problem is that Duplicacy Web (at least v1.2.1) updates its configuration by deleting and recreating duplicacy.json, which breaks the symlink. Thus, /etc/duplicacy/duplicacy.json is not updated and the new configuration is not saved.