JonathanTreffler / backblaze-personal-wine-container

Run the Backblaze personal backup client in a docker container
https://hub.docker.com/r/tessypowder/backblaze-personal-wine
GNU Affero General Public License v3.0
374 stars 35 forks source link

Unable to detect drive to backup #34

Open rohankapoorcom opened 1 year ago

rohankapoorcom commented 1 year ago

Hi - I believe I've the installation instructions correctly but the Backblaze client never shows any drive except for C or Z in the Hard Drives section.

~$ sudo docker exec --user app backblaze-backup-backblaze-1 ls -la /config/wine/dosdevices/
total 8
drwxr-xr-x 2 app app 4096 Nov  2 00:11 .
drwxr-xr-x 4 app app 4096 Nov  2 00:09 ..
lrwxrwxrwx 1 app app   10 Nov  2 00:04 c: -> ../drive_c
lrwxrwxrwx 1 app app    9 Nov  2 00:11 d: -> /drive_v/
lrwxrwxrwx 1 app app    1 Nov  2 00:04 z: -> /

When I run ~$ sudo docker exec --user app backblaze-backup-backblaze-1 wine explorer, I do see drive D mounted correctly.

I've tried both the latest tag as well as the ubuntu18 tag. Any other troubleshooting suggestions?

Thanks!

plupien79 commented 1 year ago

I also have this issue. Drive is mapped and I can see /drive_d in the directory, but not as a D: drive.

plupien79 commented 1 year ago

docker exec --user app Backblaze_Personal_Backup ln -s /drive_d/ /config/wine/dosdevices/d:

That command resolved my issue.

rohankapoorcom commented 1 year ago

I can confirm that this did not solve my issue. The drive is visible in the explorer window as D, but never shows up in the Backblaze client.

dotbanana commented 1 year ago

I have the same issue but i have to mention here that it only fails if i try to symlink a network smb-mount. Symlinking local folders works. I'm going to try it with an rsync mount too. Seems that Backblaze is somehow recognizing that those are network shares and this fact is driving me crazy really because it's such a simple task: Mount a network share as local drive share. Should be one little command. But it seems to be magic for linux or windows.

I should mention that i do not use this Docker container but i set wine up myself, but ran into the exact same problem as described here.

JonathanTreffler commented 1 year ago

I have the same issue but i have to mention here that it only fails if i try to symlink a network smb-mount. Symlinking local folders works. I'm going to try it with an rsync mount too. Seems that Backblaze is somehow recognizing that those are network shares and this fact is driving me crazy really because it's such a simple task: Mount a network share as local drive share. Should be one little command. But it seems to be magic for linux or windows.

Is the smb mount done outside the container with a docker mount to forward it into the container or is the smb mount inside the container ?