Hi,
I am using cryptomator to mount a virtual drive on Windows 11. This virtual drive contains code files that I would like to work on in WSL (specifically, using WSL through VSCode on Windows). Using the WinFsp volume type, the virtual drive is not accessible in WSL. Instead, I am using the WinFsp (Local Drive) option, which does allow for access under the /mnt directory in WSL.
The first issue I’m having is that file permissions of files in the virtual drive cannot be changed in WSL. I have enabled the “metadata” option (Advanced settings configuration in WSL | Microsoft Learn) in the wsl config, which should allow for chmod permission changes to be applied. I have tested that this works on other drives mounted from Windows, for example, for files in my C drive mounted under /mnt/c in WSL. Changing file permissions seems to not work specifically for cryptomator virtual drives.
The second issue I’m experiencing is with creating links. For example, I get the following exception in WSL: “FileSystemException: Cannot create link, path = (OS Error: Invalid argument, errno = 22)”
Does anyone successfully access a cryptomator virtual drive through WSL without these issues? Or does anyone have any proposed fixes for these issues? Perhaps through using custom mount options on the cryptomator WinFsp side (winfsp/src/dll/fuse/fuse.c at c61679a35d041d843173fa3b2eba106b5ab7b01f · winfsp/winfsp · GitHub) and/or the WSL config side (see first link above)?
If you need anymore information, please let me know.
Any help is appreciated, thank you!
Below are the technical details of my system:
wsl.exe --version output:
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.3880
WIndows specifications:
Edition: Windows 11 Pro
Version: 23H2
OS build: 22631.3880
Experience: Windows Feature Experience Pack 1000.22700.1020.0
Cryptomator version:
1.13.0