|
|
|
|
|
by folkrav
2008 days ago
|
|
WSL1 was more or less the reverse-equivalent of WINE as I understood it, more or less a translation layer for a subset of syscalls, the approach is awfully limited from the get go. Not sure how using a VHDX or partition would solve that. We'd be back to square one, with things like containers being unusable again. |
|
The problem with WSL1 is limited to disk IO performance, because the compatibility layer that's easy to do with system calls isn't so easy to do with the filesystem.
> We'd be back to square one, with things like containers being unusable again.
It's complementary. WSL2 when you play with containers, WSL1 when you don't.
Personally, I don't bother with containers for about 90% of the development cycle - and it's just for testing before being deployed to a genuine linux, not some VM.
Also, if you want to run servers with WSL (say, postgres), having containers is the last of your problems.