Closed felixschndr closed 4 months ago
Well, I am pretty sure it does read BORG_REPO.
But, what we have here is like an argument parsing issue with the positional arguments:
It expects at least REPOSITORY_OR_ARCHIVE and MOUNTPOINT, plus optionally PATH.
So, try that:
borg mount :: /mnt/test # mount whole repo (using BORG_REPO env var)
borg mount ::ARCHIVE /mnt/test # mount one archive (using BORG_REPO env var)
https://borgbackup.readthedocs.io/en/stable/usage/mount.html - guess we should have these examples there also.
Note: this issue (and the doc updates) do not apply to master branch (borg2):
In borg2, the repo is given either by a -r REPO
option or read from BORG_REPO
env var. Because it is an option and not a positional argument, giving it or leaving it away does not shift positions of the positional arguments.
Fixed in 1.2-maint and 1.4-maint. No fix needed for master.
Thank you :)
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
bug / issue
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.2.0
Since Ubuntu apt only has this old version available I am not sure that this is not fixed with a new version however I did not find anything in the changelog in a glance.
Operating system (distribution) and version.
Ubuntu 22.04
Describe the problem you're observing.
Borg
mount
does not use theBORG_REPO
env variable.In my shell I
export
edBORG_REPO
andBORG_PASSPHRASE
. When runningborg list
I don't have to supply the repo or password (as expected). When runningborg mount
I get the following error:Running
borg mount $BORG_REPO /mnt/test
works. So it uses theBORG_PASSPHRASE
automatically, just not theBORG_REPO
.I'd expect
borg mount /mnt/test
to run (the same asborg list
) without asking for a password (which it does not, so no change needed there) and without asking for a repo (which is does, change needed there)