-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forgetoption Could not parse config file! #315
Comments
I have the same issue with Debian 12. Any news here? |
The same happens to |
Manually remove the offending yaml key (forgetoption and maybe a few more) as a workaround. |
I tried this, but the invalid keys re-appear. UPDATE: I was missing env variables, after providing proper env it worked. |
cant you please explain how did you do that? what is the correct env config? cant find anythig in docs :( |
correct config should look like this, once the config is correct, manually removing the offending keys in temporary yaml will work.
when I was getting this error, .autorestic.env was not providing correct keys for bb-data backend. |
I'm seeing the same issue on Arch Linux and FreeBSD 14. Using SFTP as only backend.
|
I too was having this issue. Thank you @zkhan93 for giving me the clue. Indeed, when I added the missing repository key everything started working fine. Still, this issue should be corrected and a more adequate error raised. |
Describe the bug
i am not able to create an backup with an simple autorestic.yml
my autorestic.yaml file
`version: 2
locations:
my-locations:
from: /data
to: hdd
backends:
hdd:
type: local
path: /backup`
Expected behavior
responce from the
autoresctic check
'autorestic check
Using config: /root/.autorestic.yaml
Using lock: /root/.autorestic.lock.yml
Saved a backup copy of your file next to the original.
Initializing backend "hdd"...
Everything is fine.'
error output while
autorestic backup -a
'autorestic backup -a
Using config: /root/.autorestic.yaml
1 error(s) decoding:
Could not parse config file!
Using lock: /root/.autorestic.lock.yml'
why i get this responce ?
has invalid keys: forgetoption Could not parse config file!
Environment
The text was updated successfully, but these errors were encountered: