restic restore of externally created snapshot fails in Docker due to lchown: invalid argument #610
-
|
Hello, we installed backrest on Docker and also installed it on an proxmox container. The Backup is done seperatly without using backrest. I can set everything up in backrest and see the repositorys, snapshots and files. I also can brows the snapshots. But if i like to restore a file it get an erro code: " failed: exit code 1: restore failed" what is the problem? Thanks for your help |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
You should see a "view logs" button next to the restore operation -- click this for more detailed output re: why your restore command failed. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Thank you
|
Beta Was this translation helpful? Give feedback.
-
|
Hmm -- it looks like you're running into something related to restic/restic#655 . At the time, the reported issue is a user trying to run a restore that chown's files without root. In docker, it's more likely that this is a problem with how user IDs are mapped into the container. Backrest is supported in docker because it's by far the easiest way to get started with backups -- and I'd rather people have easy to setup backups than no backups at all :) but there are a number of footguns especially with user ID mapping and filesystem permissions when using a virtual filesystem layer in between restic the dataset. My suspicion is that there are uid's / gid's specified in the backup that don't exist in the docker container and so backrest is unable to restore those permissions. You'll probably need a bare-metal (non-dockerized install) of backrest to restore your externally created snapshots. Backrest should work fine in this sort of setup for any backups created inside the container. |
Beta Was this translation helpful? Give feedback.
-
|
hello gareth, thanks a lot. |
Beta Was this translation helpful? Give feedback.
Hmm -- it looks like you're running into something related to restic/restic#655 . At the time, the reported issue is a user trying to run a restore that chown's files without root.
In docker, it's more likely that this is a problem with how user IDs are mapped into the container.
Backrest is supported in docker because it's by far the easiest way to get started with backups -- and I'd rather people have easy to setup backups than no backups at all :) but there are a number of footguns especially with user ID mapping and filesystem permissions when using a virtual filesystem layer in between restic the dataset.
My suspicion is that there are uid's / gid's specified in the backup that don't…