Support symlinks on mounted volumes in Windows 10 Client and Hyper isolation mode
Today when using Windows Server Containers (--isolation=process) when using a mounted volumes you can create symlinks inside them as you would in any other folder. However when using Hyperv isolation, thous when using Windows 10 container Support, mounted volumes do not support symlinks.
mklink a.txt b.txt
Inside a mounted volume returns Access Denied error
Symlinks are used by most of the developments tools, like git or npm, so no supporting this is blocking every enterprise that wants to leverage containers for development, thus using Windows 10 client as development operating system.
Another option could be to "just" support Windows Container in Windows 10, removing the need for installing Hyper-V and having to deal with virtual adapters...