search

borgmatic-collective / docker-borgmatic

Borgmatic in Docker
GNU General Public License v3.0
314 stars 88 forks source link

How to do extracts with read-write source volumes? #253

Open witten opened 10 months ago

witten commented 10 months ago

As I recently discovered when extracting from backup on a reinstalled system: Read-only source volumes (as currently documented) prevent docker-borgmatic from extracting any backup files to their original locations!

Which raises the question, what's the extract story with docker-borgmatic? Is the user intended to restart the container with read-write source volume mounts whenever they need to do an extract? Or maybe source volumes should be documented as read-write by default, at the cost of some decreased security? I'm of course open to suggestions.. There doesn't seem like a clear-cut answer here.

This might just be a documentation issue. There is the existing section about restoring backups, but it seems FUSE oriented. Maybe that's the intended way to restore backups rather than with extract?

notflip commented 9 months ago

I'm also having issues extracting using docker..

Test Local on BorgBase: Error running actions for repository
Command 'borg extract ssh://USER@URL.repo.borgbase.com/./repo::6e50ee4e5df9-2023-10-03-071544' returned non-zero exit status 1.
Test Local on BorgBase: Retrying... attempt 1/5
Test Local on BorgBase: Sleeping 5s before next retry
Test Local on BorgBase: Error running actions for repository
Command 'borg extract ssh://USER@URL.repo.borgbase.com/./repo::6e50ee4e5df9-2023-10-03-071544' returned non-zero exit status 1.
Test Local on BorgBase: Retrying... attempt 2/5
Test Local on BorgBase: Sleeping 10s before next retry
witten commented 9 months ago

You might try upping your verbosity --verbosity 2 and/or disabling retries in configuration to see what might be going on there.