link🐳 Docker

The docker image is build with rclone and restic already included. It's ment more as a utility image.

linkRemote hosts

For remote backups (S3, B2, GCS, etc.) it's quite easy, as you only need to mount the config file and the data to backup.

1link$docker run --rm \\

2link$  -v $(pwd):/data \\

3link$  cupcakearmy/autorestic \\

4link$  autorestic backup -va -c /data/.autorestic.yaml

linkCron

To use cron with the docker image, you have 2 environment variables. AUTORESTIC_INITIAL_ARGS and CRON_CONFIG_DIR

• AUTORESTIC_INITIAL_ARGS is arguments used for the initial autorestic command on container start up, if you don't set it, autorestic would show available commands.

For example:

1linkAUTORESTIC_INITIAL_ARGS=backup -va -c /.autorestic.yaml

Would mean autorestic backup -va -c /.autorestic.yaml on container startup.

• CRON_CONFIG_DIR to enable Cron, you need to set this to the in-contaier directory of the config file you want to use with Cron.

linkExample

1linkversion: '3.3'

2link

3linkservices:

4link  autorestic:

5link    image: cupcakearmy/autorestic:latest

6link    environment:

7link      - AUTORESTIC_INITIAL_ARGS=backup -va -c /.autorestic.yaml

8link      - CRON_CONFIG_DIR=/.autorestic.yaml

9link    volumes:

10link      - ./autorestic.yaml:/.autorestic.yaml

This would run autorestic backup -va -c /.autorestic.yaml on container startup, and check for any backups due in /.autorestic.yaml.

linkRclone

For rclone you will have to also mount the rclone config file to /root/.config/rclone/rclone.conf.

To check where it is located you can run the following command: rclone config file.

Example

1link$docker run \\

2link$  -v /home/user/.config/rclone/rclone.conf:/root/.config/rclone/rclone.conf:ro \\

3link$  ...