{"id":22301572,"url":"https://github.com/vividboarder/docker-duplicity-cron","last_synced_at":"2025-07-29T02:32:39.912Z","repository":{"id":18851850,"uuid":"85439804","full_name":"ViViDboarder/docker-duplicity-cron","owner":"ViViDboarder","description":"Use Docker to automate backups to a variety of destinations supported by Duplicity","archived":false,"fork":false,"pushed_at":"2021-12-28T05:53:42.000Z","size":52,"stargazers_count":5,"open_issues_count":3,"forks_count":2,"subscribers_count":2,"default_branch":"master","last_synced_at":"2023-03-10T20:18:40.677Z","etag":null,"topics":["amazon-s3","backups","docker","duplicity"],"latest_commit_sha":null,"homepage":null,"language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ViViDboarder.png","metadata":{"files":{"readme":"Readme.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2017-03-19T00:00:43.000Z","updated_at":"2022-03-19T00:38:17.000Z","dependencies_parsed_at":"2022-08-31T04:52:57.437Z","dependency_job_id":null,"html_url":"https://github.com/ViViDboarder/docker-duplicity-cron","commit_stats":null,"previous_names":[],"tags_count":0,"template":null,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ViViDboarder%2Fdocker-duplicity-cron","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ViViDboarder%2Fdocker-duplicity-cron/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ViViDboarder%2Fdocker-duplicity-cron/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ViViDboarder%2Fdocker-duplicity-cron/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ViViDboarder","download_url":"https://codeload.github.com/ViViDboarder/docker-duplicity-cron/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":227973183,"owners_count":17849638,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["amazon-s3","backups","docker","duplicity"],"created_at":"2024-12-03T18:23:16.912Z","updated_at":"2024-12-03T18:23:18.149Z","avatar_url":"https://github.com/ViViDboarder.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Duplicity Backup\n\n## Archived\nI've moved on to using [Restic Scheduler](https://git.iamthefij.com/iamthefij/restic-scheduler)\n\n## Instructions\nMount any directories you'd like to back up as a volume and run\n\n## Env Variables\n| Variable | Default | Description |\n| -------- | ------- | ----------- |\n|AWS_ACCESS_KEY_ID| |Required for writing to S3|\n|AWS_DEFAULT_REGION| |Required for writing to S3|\n|AWS_SECRET_ACCESS_KEY| |Required for writing to S3|\n|BACKUP_DEST|file:///backups|Destination to store backups (See [duplicity documenation](http://duplicity.nongnu.org/duplicity.1.html#sect7))|\n|BACKUP_NAME|backup|What the name for the backup should be. If using a single store for multiple backups, make sure this is unique|\n|CLEANUP_COMMAND| |An optional duplicity command to execute after backups to clean older ones out (eg. \"remove-all-but-n-full 2\")|\n|CRON_SCHEDULE| |If you want to periodic incremental backups on a schedule, provide it here. By default we just backup once and exit|\n|FLOCK_WAIT|60|Seconds to wait for a lock before skipping a backup|\n|FTP_PASSWORD| |Used to provide passwords for some backends. May not work without an attached TTY|\n|FULL_CRON_SCHEDULE| |If you want to periodic full backups on a schedule, provide it here. This requires an incremental cron schedule too|\n|GPG_KEY_ID| |The ID of the key you wish to use. See [Encryption](#encryption) section below|\n|OPT_ARGUMENTS| |Any additional arguments to provide to the duplicity backup command|\n|PASSPHRASE|Correct.Horse.Battery.Staple|Passphrase to use for GPG|\n|PATH_TO_BACKUP|/data|The path to the directory you wish to backup. If you want to backup multiple, see the [tip below](#backing-up-more-than-one-source-directory)|\n|RESTORE_ON_EMPTY_START| |Set this to \"true\" and if the `$PATH_TO_BACKUP` is empty, it will restore the latest backup. This can be used for auto recovery from lost data|\n|SKIP_ON_START| |Skips backup on start if set to \"true\"|\n|VERIFY_CRON_SCHEDULE| |If you want to verify your backups on a schedule, provide it here|\n\n## Encryption\nBy default Duplicity will use a symettric encryption using just your passphrase. If you wish to use a GPG key, you can add a ro mount to your `~/.gnupg` directory and then provide the `GPG_KEY_ID` as an environment variable. The key will be used to sign and encrypt your files before sending to the backup destination.\n\nNeed to generate a key? Install `gnupg` and run `gnupg --gen-key`\n\n## Tips\n\n### Missing dependencies?\nPlease file a ticket! Duplicity supports a ton of backends and I haven't had a chance to validate that all dependencies are present in the image. If something is missing, let me know and I'll add it\n\n### Getting complains about no terminal for askpass?\nInstead of using `FTP_PASSWORD`, add the password to the endpoint url\n\n### Backing up more than one source directory\nDuplicity only accepts one target, however you can refine that selection with `--exclude` and `--include` arguments. The below example shows how this can be used to select multiple backup sources\n```\nOPT_ARGUMENTS=\"--include /home --include /etc --exclude '**'\"\nPATH_TO_BACKUP=\"/\"\n```\n\n### Backing up from another container\nMount all volumes from your existing container with `--volumes-from` and then back up by providing the paths to those volumes. If there are more than one volumes, you'll want to use the above tip for mulitple backup sources\n\n### Restoring a backup\nOn your running container, execute `/restore.sh`. That should be that! Eg. `docker exec my_backup_container /restore.sh`\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fvividboarder%2Fdocker-duplicity-cron","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fvividboarder%2Fdocker-duplicity-cron","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fvividboarder%2Fdocker-duplicity-cron/lists"}