Maybe I state the obvious here but anyway:
Tonight I found a super comfi way to browse and restore data from Borg repositories. In vorta you can add any existing borg repository and mount the containing backups in a very functional GUI. Until now I somehow assumed you could only deal with backups created in vorta which is not true.
For context let me explain why I find that so useful: I am using a wonderful Borg / Borgmatic container from the borgmatic collective. It works super reliable. But for restoring files you have to mount the backup in the container and deal with the files inside the container. This can be difficult i.e. when looking for a specific file in a folder with a lot of files (like a foto collection where you accidentally deleted one file).
If any Borg users are out there: I would be interested what your workflows look like.
Borg is running on a headless server. Everything is dockerized, so I did the same with Borg. Advantages are that the setup is easy to setup, backup the config and move it to a different server. At first I did not realize that the mount of the backup only exists in the container and that this is making things a little harder.
Could you mount a blank directory into docker, then use borg to mount the backups into that?
This was the first idea. I cannot explain very well why this does not work. But I think the issue is that the borg mount magic lives inside the container so the filesystem cannot be seen from the host. You can mount an empty directory and copy the files you want to access from the host into it. Problem with that is that you are stuck with the tooling provided by the container.