Description
Describe the bug
The documentation claims that if the restic
binary isn't found, it will be downloaded from GitHub releases. I've found this to not be the case.
To Reproduce
Steps to reproduce the behavior:
- Go to http://localhost:9898/#/getting-started
- Click on 'Add Repo'
- Enter an S3 repo
- Click "Test configuration"
The following error pops up:
Check error: : [unknown] command "/root/.local/share/backrest/restic cat config -o sftp.args=-oBatchMode=yes" failed: fork/exec /root/.local/share/backrest/restic: no such file or directory
Expected behavior
-
Could Backrest search for
restic
(orrestic-{VERSION}
in$PATH
, instead of in the two hardcoded locations mentioned in Binary Management? -
Can there be an initial screen setting up restic, before the user wastes time configuring a repo, only to find out restic wasn't detected?
-
I had moved
restic
to /bin/ and renamed it as described at Binary Management. But the error above only listed/root/.local/share/backrest/restic
, not/bin/
.
$ /bin/restic-0.18.0 version
restic 0.18.0 compiled with go1.24.1 on linux/amd64
- Also, the error shows that Backrest is looking for
restic
, not forrestic-{$VERSION}
as the documentation claims.
Am I doing something stupid here? How can onboarding be so broken?
Screenshots
Platform Info
- OS and Architecture Linux x64
- Backrest Version 1.8.0