4 ms·
On WSL2, Microsoft has their own init with another container launched for multiple reasons: - That other container, the WSL system distribution has a Wayland a
by my123 5y ago
On WSL2, Microsoft has their own init with another container launched for multiple reasons:
- That other container, the WSL system distribution has a Wayland and a PulseAudio server for graphics integration.
- in a regular WSL config, the VM completely closes 60 seconds after the last terminal is. If you have daemons running, that cannot be guaranteed to work anymore.
- compatibility of distributions across WSL1 and WSL2, the former which has a significantly lower feature set.