Found my first issue with using a Dev Drive, and wanting to have access to it from WSL: apparently the way Dev Drives mount in Windows is not compatible with the WSL auto-mounting.
Why does this matter? Docker Desktop (in WSL 2 mode) can't mount a Dev Drive folder.
Do I dump WSL 2 mode for Docker? Or do I dump Dev Drive? Tough choice, but I suspect I dump the Dev Drive.
@bradwilson Both are underpinned by dynamic VHDX files last I checked, so the impact of storage should make little difference. In fact, WSL2 runs in containers by default. Probably a wash, then.
At the end of the day, I'm trying to run Docker mounting a folder under my C:\Dev folder (which is a mounted Dev Drive). What does VHDX or containers have to do with that?
@bradwilson I was pointing out that the performance of one over the other should be negligible i.e., there's no practical cost to switching, it would seem...assuming you don't need access to nearly all hardware resource WSL2 can see. Vanilla Docker can see most anyway.
@heaths The build times with Dev Drives is definitely faster, but not so much faster that it actually matters. The easiest path seems to be to just dump Dev Drive.
If I use a Dev Drive mounted as a drive letter, then use MKLINK /J to make a junction point from my desired local location to the Dev Drive, that's something WSL 2 does understand, and transparently translates that to a symbolic link in Linux terms. So it's really just using Disk Manager to mount it directly into the file system that's the problem.
So I can keep my Dev Drive and get Docker to volume mount things for me again! 🎉
Add comment