Open rohankapoorcom opened 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.
docker exec --user app Backblaze_Personal_Backup ln -s /drive_d/ /config/wine/dosdevices/d:
That command resolved my issue.
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.
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.
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 ?
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.
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!