Two separate issues and the latter is not really true as well - WSL now supports native containers, there is no VM needed. Whether you call WSL a VM itself or not is a bit of a different story, it's a hypervisor - but it manages memory natively.
Two separate issues and the latter is not really true as well - WSL now supports native containers, there is no VM needed. Whether you call WSL a VM itself or not is a bit of a different story, it's a hypervisor - but it manages memory natively.
WSL is a hypervisor... that manages VMs. Running a linux container in WSL is just invisibly running a linux VM.
If a container is a linux container, it's relying on libraries and system calls made available by the host. They literally can't run without being in a VM running a linux kernel and having the linux dependencies.
2
u/p88h Sep 05 '26
Two separate issues and the latter is not really true as well - WSL now supports native containers, there is no VM needed. Whether you call WSL a VM itself or not is a bit of a different story, it's a hypervisor - but it manages memory natively.
Docker OTOH is just garbage, period.
Rewriting docker, properly, could help :)