WIP: Let's get restic in here

Dockerfile.ubuntu

@@ -1,46 +1,22 @@
-FROM ubuntu:xenial
+FROM ubuntu:artful
 MAINTAINER ViViDboarder <vividboarder@gmail.com>
 
 RUN apt-get update \
-        && apt-get install -y --no-install-recommends \
-            software-properties-common python-software-properties \
-        && add-apt-repository ppa:duplicity-team/ppa \
-        && apt-get update \
         && apt-get install -y --no-install-recommends \
             cron \
-            duplicity \
+            restic \
-            lftp \
-            ncftp \
-            openssh-client \
-            python-cloudfiles \
-            python-gdata \
-            python-oauthlib \
-            python-paramiko \
-            python-pexpect \
-            python-pip \
-            python-setuptools \
-            python-swiftclient \
-            python-urllib3 \
-            rsync \
-            tahoe-lafs \
-        && pip install -U boto b2 \
-        && apt-get autoremove -y python-pip \
         && apt-get clean \
         && rm -rf /var/apt/lists/*
 
-VOLUME /root/.cache/duplicity
+VOLUME /root/.cache/restic
 VOLUME /backups
-VOLUME /var/lock/duplicity
 
-ENV BACKUP_DEST="file:///backups"
+ENV BACKUP_DEST="/backups"
 ENV BACKUP_NAME="backup"
 ENV PATH_TO_BACKUP="/data"
-ENV PASSPHRASE="Correct.Horse.Battery.Staple"
-ENV FLOCK_WAIT=60
 
 # Cron schedules
 ENV CRON_SCHEDULE=""
-ENV FULL_CRON_SCHEDULE=""
 ENV VERIFY_CRON_SCHEDULE=""
 
 ADD backup.sh /

Makefile

@@ -1,4 +1,4 @@
-DOCKER_TAG ?= docker-duplicity-cron
+DOCKER_TAG ?= docker-restic-cron
 
 .PHONY: default
 default: build-x86

Readme.md

@@ -1,6 +1,6 @@
-# Duplicity Backup
+# Restic Backup
 
-[![Build Status](https://travis-ci.org/ViViDboarder/docker-duplicity-cron.svg?branch=master)](https://travis-ci.org/ViViDboarder/docker-duplicity-cron)
+[![Build Status](https://travis-ci.org/ViViDboarder/docker-restic-cron.svg?branch=master)](https://travis-ci.org/ViViDboarder/docker-restic-cron)
 
 ## Instructions
 Mount any directories you'd like to back up as a volume and run
@@ -11,7 +11,7 @@ Mount any directories you'd like to back up as a volume and run
 |AWS_ACCESS_KEY_ID| |Required for writing to S3|
 |AWS_DEFAULT_REGION| |Required for writing to S3|
 |AWS_SECRET_ACCESS_KEY| |Required for writing to S3|
-|BACKUP_DEST|file:///backups|Destination to store backups (See [duplicity documenation](http://duplicity.nongnu.org/duplicity.1.html#sect7))|
+|BACKUP_DEST|/backups|Destination to store backups (See [duplicity documenation](http://duplicity.nongnu.org/duplicity.1.html#sect7))|
 |BACKUP_NAME|backup|What the name for the backup should be. If using a single store for multiple backups, make sure this is unique|
 |CLEANUP_COMMAND| |An optional duplicity command to execute after backups to clean older ones out (eg. "remove-all-but-n-full 2")|
 |CRON_SCHEDULE| |If you want to periodic incremental backups on a schedule, provide it here. By default we just backup once and exit|
@@ -26,11 +26,6 @@ Mount any directories you'd like to back up as a volume and run
 |SKIP_ON_START| |Skips backup on start if set to "true"|
 |VERIFY_CRON_SCHEDULE| |If you want to verify your backups on a schedule, provide it here|
 
-## Encryption
-By 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.
-
-Need to generate a key? Install `gnupg` and run `gnupg --gen-key`
-
 ## Tips
 
 ### Missing dependencies?

backup.sh

@@ -1,25 +1,16 @@
 #! /bin/bash
 set -e
 
-(
+restic \
-    if ! flock -x -w $FLOCK_WAIT 200 ; then
+    -r $BACKUP_DEST \
-        echo 'ERROR: Could not obtain lock. Exiting.'
-        exit 1
-    fi
-
-    duplicity \
-        $1 \
-        --asynchronous-upload \
-        --log-file /root/duplicity.log \
-        --name $BACKUP_NAME \
     $OPT_ARGUMENTS \
+    backup \
     $PATH_TO_BACKUP \
-        $BACKUP_DEST
+    --tag $BACKUP_NAME \
 
 if [ -n "$CLEANUP_COMMAND" ]; then
-        duplicity $CLEANUP_COMMAND \
+    restic \
-            --log-file /root/duplicity.log \
+        -r $BACKUP_DEST \
-            --name $BACKUP_NAME \
+        forget \
-            $BACKUP_DEST
+        $CLEANUP_COMMAND
 fi
-) 200>/var/lock/duplicity/.duplicity.lock

restore.sh

@@ -1,18 +1,11 @@
 #! /bin/bash
 set -e
 
-(
+restore_snapshot=$1
-    if ! flock -x -w $FLOCK_WAIT 200 ; then
-        echo 'ERROR: Could not obtain lock. Exiting.'
-        exit 1
-    fi
 
-    duplicity restore \
+restic \
-        --force \
+    -r $BACKUP_DEST \
-        --log-file /root/duplicity.log \
-        --name $BACKUP_NAME \
     $OPT_ARGUMENTS \
-        $@ \
+    restore \
-        $BACKUP_DEST \
+    $restore_snapshot \
-        $PATH_TO_BACKUP
+    -t /
-) 200>/var/lock/duplicity/.duplicity.lock

start.sh

@@ -11,14 +11,12 @@ if [ "$OPT_ARGUMENTS" == "" ]; then
     export OPT_ARGUMENTS="$@"
 fi
 
-# If key id is provied add arg
+# Init the repo
-if [ -e "$GPG_KEY_ID" ]; then
+restic -r $BACKUP_DEST snapshots || restic -r $BACKUP_DEST init
-    export OPT_ARGUMENTS="$OPT_ARGUMENTS --encrypt-sign-key=\"$GPG_KEY_ID\""
-fi
 
 # If set to restore on start, restore if the data volume is empty
 if [ "$RESTORE_ON_EMPTY_START" == "true" -a -z "$(ls -A $PATH_TO_BACKUP)" ]; then
-    /restore.sh
+    /restore.sh latest
 fi
 
 # Unless explicitly skipping, take a backup on startup
@@ -39,11 +37,6 @@ if [ -n "$CRON_SCHEDULE" ]; then
     echo "$CRON_SCHEDULE source /env.sh && /backup.sh 2>> /cron.log" >> /crontab.conf
     echo "Backups scheduled as $CRON_SCHEDULE"
 
-    if [ -n "$FULL_CRON_SCHEDULE" ]; then
-        echo "$FULL_CRON_SCHEDULE source /env.sh && /backup.sh full 2>> /cron.log" >> /crontab.conf
-        echo "Full backup scheduled as $VERIFY_CRON_SCHEDULE"
-    fi
-
     if [ -n "$VERIFY_CRON_SCHEDULE" ]; then
         echo "$VERIFY_CRON_SCHEDULE source /env.sh && /verify.sh 2>> /cron.log" >> /crontab.conf
         echo "Verify scheduled as $VERIFY_CRON_SCHEDULE"
@@ -52,9 +45,9 @@ if [ -n "$CRON_SCHEDULE" ]; then
     # Add to crontab
     crontab /crontab.conf
 
-    echo "Starting duplicity cron..."
+    echo "Starting restic cron..."
     cron
 
-    touch /cron.log /root/duplicity.log
+    touch /cron.log
-    tail -f /cron.log /root/duplicity.log
+    tail -f /cron.log
 fi

tests/docker-compose-test-s3.yml

@@ -1,17 +1,17 @@
 version: '2'
 services:
-  duplicity:
+  restic:
     build:
       context: ..
       dockerfile: Dockerfile.${DOCKER_BASE}
     entrypoint: "bash"
-    command: ["/test.sh"]
+    command: "-c 'sleep 2 && /test.sh'"
     hostname: itest
     environment:
       IN_CONTAINER: 'true'
       SKIP_ON_START: 'true'
-      OPT_ARGUMENTS: '--s3-unencrypted-connection'
+      RESTIC_PASSWORD: Correct.Horse.Battery.Staple
-      BACKUP_DEST: s3://minio:9000/duplicity
+      BACKUP_DEST: s3:http://minio:9000/restic
       AWS_DEFAULT_REGION: us-east-1
       AWS_ACCESS_KEY_ID: SUPER_SECRET_ACCESS_KEY
       AWS_SECRET_ACCESS_KEY: SUPER_SECRET_SECRET_KEY

tests/test.sh

@@ -1,4 +1,5 @@
 #! /bin/bash
+set -e
 
 image=$1
 
@@ -7,6 +8,7 @@ if [ "$IN_CONTAINER" != "true" ] ; then
     docker run --rm \
         -e IN_CONTAINER=true \
         -e SKIP_ON_START=true \
+        -e RESTIC_PASSWORD="Correct.Horse.Battery.Staple" \
         -v "$(pwd)/test.sh:/test.sh" \
         $image \
         bash -c "/test.sh"
@@ -20,6 +22,9 @@ else
     echo "Create test data..."
     mkdir -p /data && echo Test > /data/test.txt
 
+    echo "Fake a start and init repo"
+    CRON_SCHEDULE="" /start.sh
+
     echo "Making backup..."
     /backup.sh
 
@@ -33,7 +38,10 @@ else
     test -f /data/test.txt && exit 1 || echo "Gone"
 
     echo "Restore backup..."
-    /restore.sh
+    /restore.sh latest
+
+    echo "Verify restore..."
+    cat /data/test.txt
 
     echo "Verify backup..."
     /verify.sh
@@ -48,11 +56,9 @@ else
     RESTORE_ON_EMPTY_START=true /start.sh
 
     echo "Verify restore happened..."
-    test -f /data/test.txt
+    cat /data/test.txt
 
     echo "Verify restore with incorrect passphrase fails..."
-    export PASSPHRASE=Incorrect.Mule.Solar.Paperclip
-
     echo "Fail to restore backup..."
-    /restore.sh && exit 1 || echo "OK"
+    RESTIC_PASSWORD=Incorrect.Mule.Solar.Paperclip /restore.sh latest && exit 1 || echo "OK"
 fi

verify.sh

@@ -1,10 +1,7 @@
 #! /bin/bash
 set -e
 
-duplicity verify \
+restic \
-    --compare-data \
+    -r $BACKUP_DEST \
-    --log-file /root/duplicity.log \
-    --name $BACKUP_NAME \
     $OPT_ARGUMENTS \
-    $BACKUP_DEST \
+    check
-    $PATH_TO_BACKUP