TibixDev
[Feature] Add a shared folder that is not only limited to /home/$USER
Feature Description
I think it would be a good idea to add an option to only allow the windows container to only access a smaller part of the host filesystem.
Use-Case
This would be useful for people that do not want windows to have access to there home directory or any sensitive data there.
Proposed Implementation
I would change the current option of Shared home folder to have a browse function so you can set what folder you want the container to access.
Notice
- [x] I have checked the issue tracker and verified that this Feature Request has not been proposed before.
- [ ] I would like to help out implementing this feature
I would like this feature to be added. Exposing the entire home folder to windows is pretty risky, since there is possibility that if windows gets infected, linux home folder files becomes corrupted too
I think it would be more safe to expose just one folder to windows, so it acts like a mailbox between your linux system and windows container. There are some apps in windows in which we may have to bring a file from linux to windows and import it to the app to work with it. Having a seperate shared folder between linux and windows to make your work easy with apps without exposing your entire linux home would be amazing
This may be addressed fully in a future feature. For now you can disable sharing your home directory with the guest VM and instead use SMB to share individual directories with the guest.
It seems like this would be as simple as adding the --volume (with the path of the folder that should be shared from your host system) in the docker launch command (see https://docs.docker.com/get-started/docker-concepts/running-containers/sharing-local-files/ for more information)
Is there any reason this wouldn't work?
smb is a good idea I didn't think about that. I currently just use a usb drive and pass it through to the container and back.
smb is a good idea I didn't think about that. I currently just use a usb drive and pass it through to the container and back.
I like it because you don't have to re-compose, and you can have per-dir access controls (no root or w.e middleman). I do find that to access the share on my host I have to use its LAN IP, YMMV.
Windows comes with an SSH client so I just use that via cmd. There's also a setting to enable an SSH server. Setting up SMB is too much drudge work for me, but sometimes it's more worth it. For simple file transfer SSH is perfect tho.
