Linux permission not restored even if I use "restore-permissions"

I’ve just discover Duplicati a couple of hours ago but I already love it!

My only issue so far is that when I try to restore a backup locally, it fail to restore files and folders permissions. My source and destination are to folder on the same hdd and I’m not using encryption.

By the way I’m running Duplicati within a docker container. Both source and destination have full read/write access (777).

Someone have a clue for me? Thanks!

Here’s the restore log:

FilesRestored: 0
SizeOfRestoredFiles: 0
FoldersRestored: 0
SymlinksRestored: 0
FilesPatched: 0
FilesDeleted: 0
FoldersDeleted: 0
SymlinksDeleted: 0
MainOperation: Restore
RecreateDatabaseResults: null
ParsedResult: Warning
EndTime: 8/17/2017 11:48:41 PM
BeginTime: 8/17/2017 11:48:40 PM
Duration: 00:00:00.3644000
Messages: [
    Searching backup 0 (8/17/2017 11:14:04 PM) ...,
    1 remote files are required to restore
Warnings: [
    Failed to apply metadata to file: "/source/Documents/", message: Invalid parameter => Invalid parameter,
    Failed to apply metadata to file: "/source/Documents/toto.txt", message: Operation not permitted => Operation not permitted
Errors: []
    RemoteCalls: 2
    BytesUploaded: 0
    BytesDownloaded: 805
    FilesUploaded: 0
    FilesDownloaded: 1
    FilesDeleted: 0
    FoldersCreated: 0
    RetryAttempts: 0
    UnknownFileSize: 0
    UnknownFileCount: 0
    KnownFileCount: 15
    KnownFileSize: 10414
    LastBackupDate: 8/17/2017 11:14:04 PM
    BackupListCount: 5
    TotalQuotaSpace: 153618755584
    FreeQuotaSpace: 140896624640
    AssignedQuotaSpace: -1
    ParsedResult: Success
1 Like

If I run it trough command line instead of webui, it works…

mono /app/duplicati/Duplicati.CommandLine.exe restore "file:///backups/" --restore-path=/source/Documents --overwrite=true --restore-permissions --no-encryption

Are you running the command outside the container?

The commandline and web(server) is using the exact same code, so the only change is the environment.

I’m running it trough an interactive docker exec of the container /bin/bash.

Should I open an issue on github? Thanks!

Yes, you can open an issue, but I think there is some kind of permission issue (Operation not permitted).

Can you reproduce this with a publicly available Docker image file?