When container-init-up-20-init.sh#L35 executes the current working directory is "/run/s6-rc:s6-rc-init:PAgNln/servicedirs/s6rc-oneshot-runner". I see that ".duplicacy" is being created in that directory rather than "/config". The only thing I have in "/config" is "preferences". As a result, downstream backup attempts fail with the message "Repository has not been initialized".
When container-init-up-20-init.sh#L35 executes the current working directory is "/run/s6-rc:s6-rc-init:PAgNln/servicedirs/s6rc-oneshot-runner". I see that ".duplicacy" is being created in that directory rather than "/config". The only thing I have in "/config" is "preferences". As a result, downstream backup attempts fail with the message "Repository has not been initialized".
I can solve this by adding 'cd "$config_dir"' above container-init-up-20-init.sh#L35. And I see that you are doing that on backup.sh#L109 before the backup call.