- Edited
Hi!
Sorry, I’m still a bit a newbie regarding docker etc. so I’m surely doing something wrong. I’m trying to setup borgmatic backup as described in
Borgmatic Backup - mailcow: dockerized documentation docs.mailcow.email
now, it’s running with tons of premission denied errors (basically all the mails I guess) and
when I see that line I guess there’s a problem with /mnt/borg-repository, too.
Command '('borg', 'create', '--exclude-from', '/tmp/tmpsgz_lt81', '--one-file-system', '--read-special', '/mnt/borg-repository::{hostname}-{now:%Y-%m-%dT%H:%M:%S.%f}', '/mnt/source', '/root/.borgmatic', '--dry-run', '--list')' returned non-zero exit status 1.
The doc states that the container uses /mnt/borg-repository for local filesystem, but I don’t understand what that means as you have to state the repository anyway, so what’s special about /mnt/borg-repository?
I put - /mnt/backup/borg:/mnt/borg-repository under services: volumes: in docker-compose.override (does it need to go into the volumes: section (root level) as well? would I have to do something different? borg backup has put some files there, so it seems to be able to access it (mnt/backup is an s3 bucket mounted with goofys)
in the borgmatic config I changed the ssh line into:
repositories:
- /mnt/borg-repository
it he problem here?
Any help is appreciated