Issues mapping the autorestic.yml file in a bind mount volume in docker #271
-
I am trying to run this using UnRAID and I am bind mounting 2 folders: 1 data folder to backup and 1 config folder in my appdata folder where all my dockers exist. I am unsure where the .autorestic.yml file is suppose to lie. I want the yml file to be in the config folder which is separate from my data folder, but regardless how I name my bind volume mounts i still have issues getting the container to run. It auto shutsdowns. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Ok so this is no longer an issue as I went ahead and stopped using the docker image and chose to directly install autorestic. It seems that the docker version of this is a container meant to be used with the docker run command as a one time use to backup. I preferred a persistent install so not using the docker method anymore. I think this is why the container wasn't continuously running as the entrypoint and CMD in the dockerfile doesn't run a continuous process. |
Beta Was this translation helpful? Give feedback.
-
I store my config in I have the following plugins installed as well:
In User Scripts, you can create a script and have it run at custom intervals. This is my script for backups: docker run --rm \
-v /mnt/user/appdata/autorestic:/data \
-v /mnt/user:/mnt/user \
-v /mnt/disks/Backup:/mnt/disks/Backup \
cupcakearmy/autorestic \
autorestic backup -va -c /data/.autorestic.yaml Note: This does create an orphaned image entry in your Docker tab in UnRAID, and you do need to download the image originally and keep it up to date. |
Beta Was this translation helpful? Give feedback.
Ok so this is no longer an issue as I went ahead and stopped using the docker image and chose to directly install autorestic. It seems that the docker version of this is a container meant to be used with the docker run command as a one time use to backup. I preferred a persistent install so not using the docker method anymore. I think this is why the container wasn't continuously running as the entrypoint and CMD in the dockerfile doesn't run a continuous process.