Duplicacy docker zip file#
This posed some problems when the source was moved around a few times, so I've moved to a different approach:Ī second project runs a download of the source every night and provides the downloaded source as a zip file as a so called "artifact" for download.
![duplicacy docker duplicacy docker](https://docs.theme-park.dev/site_assets/kitana/dark.png)
So in difference to other containers, the code is not already in the built container but downloaded in the beginning. Since the code for deemix-pyweb does not follow any release-versioning (the api behind it, deemix, does but pyweb, the webclient doesnt), the strategy is just to always pull the latest code from the repo and run it in the container, downloaded at build time. But dockerhub killed all deemix related stuff a while ago, so I moved to gitlab (even though it has slightly less functionality in regards to stats and so on). Originally, this was hosted on dockerhub. The container is working, the links are not dead or anything.Ī bit of history and a little background: Hi, I am the owner/supplier of the deemix container. Not getting too much in the way of answers though that are helping so I thought I'd post here as well. I've also opened a thread on their forums here: 15:49:13.297 INFO SNAPSHOT_DELETE Deleting snapshot Backups at revision 70 15:49:12.865 INFO SNAPSHOT_DELETE Deleting snapshot AppData at revision 71 15:49:12.337 INFO SNAPSHOT_DELETE Deleting snapshot Photos at revision 70 15:49:12.318 INFO SNAPSHOT_DELETE Deleting snapshot Paperless at revision 25 15:49:11.847 INFO SNAPSHOT_DELETE Deleting snapshot Nextcloud at revision 70 15:49:11.795 INFO SNAPSHOT_DELETE Deleting snapshot Flash at revision 74 15:49:04.782 INFO RETENTION_POLICY Keep no snapshots older than 15 days 15:49:02.652 INFO BACKBLAZE_URL download URL is: Running prune command from /cache/localhost/all Had one going where the last line on the prune log was from 5:30AM, and 10 hours later it hadn't moved.Ĭancelled and restarted it and now it's stuck here pretty quickly without any movement for ~45 minutes. In addition to my keyring issue above, I'm also having issues where the prune commands will lock up ONLY for backblaze, when I run them on local backups they run fine and snappy, but when running against backblaze they just lock up, Starting the web server at 1 09:11:33 The license may have been issued to a different computerġ 09:11:33 Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set PS - when I start the container I do see the following lines, not sure if this is related.
![duplicacy docker duplicacy docker](https://docs.theme-park.dev/site_assets/plex/aquamarine.png)
Duplicacy docker how to#
This wasn't ever an issue until Jan 21, trying to find out how to avoid that, because having to open the container's web UI on a regular basis to enter a password is killing my automated backup plan.Īny advice on what I can do to try to find out what's going on? Thanks in advance! If I do NOT give it the master password, then backup schedules fail to run.
Duplicacy docker update#
So with Duplicacy, it's happened twice lately, once with the last update (Jan 21), and then again just last night when my weekly CA appdata backup/restore runs (but no Duplicacy update happened this time) where it will ask for the master password (not the admin WebUI password).