-
Notifications
You must be signed in to change notification settings - Fork 36
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
Mounting SMB/CIFS share #67
Comments
Having the exact same problem here. |
Same exact issue here as well. Only thing that made me get remotely close was binding a folder within the share to the backblaze d drive which seemed to show up in the backblaze control panel, but would not allow me to check the drive for backup |
Has anyone made any progress on this? I have the same use case and haven't been able to find a way of making wine see the mapped mount points as normal drives. (I also tried nfs shares but they were also identified as network shares) |
I also had the same results with the NFS share. I found this post which points to a possible solution but I'm not sure what it is suggesting. Does anyone understand this post? https://forum.winehq.org/viewtopic.php?t=38594 And here is another post which is more confusing to a non-developer, but this makes me believe there is no easy way to trick the system into believing it's a local storage resource. |
Hi,
I'm running a proxmox server with a VM like OMV for share with CIFS/SMB
I have a VM for Backblaze, in /etc/fstab a cifs mount point /mnt/shared
in my docker-compose, i mount this share
- "/mnt/shared/:/drive_e/"
and create the symbolic link is ok
docker exec --user app backblaze ln -s /drive_e/ /config/wine/dosdevices/e:
But wine seems to see this like a network share
Existing any alternative for mounting a cifs/smb share ?
Thanks
The text was updated successfully, but these errors were encountered: