dockur
[Feature]: Yet another virtiofs request
Is your proposal related to a problem?
I know this has been requested before (#28, #233) and denied on performance grounds, but the lack of virtiofs as an option is limiting the usability of the project for me. I have a program that I would like to run on Windows that needs to be able to share a directory with the host, but the software has restrictions on mapped network drives. The shared folder must be presented as a directly attached volume for the program to function; the current solution of SMB share simply does not work.
Describe the solution you'd like.
I would like a way to mount host folders as virtiofs volumes on the guest. A slow but functioning solution would be better than a solution that doesn't work.
Describe alternatives you've considered.
Emulation of the Windows program via a WINE container instead of virtualization, which theoretically works but has other unrelated compatibility issues.
Additional context
No response
This is something I would really love to see as well, there are several programs that exist that check if a drive is a mapped network drive, or a local drive and based on that let you use them or not. In my case I am using Dokany which lets me map a samba UNC mount to a fake drive letter, but honestly I would much rather take the performance hit and go direct to the underlying file store. It seems like the VirtIOFS has become much more stable, and it would be great to have a second option to allow for drives or paths to be created and linked to the underlying Filesystem without having to use network mounts or bind mounts, so the system thinks it’s an actual drive or path.
