![]() ![]() So currently you need to opt-in to enable systemd for a specific WSL distro, and we will monitor feedback and investigate making this behavior by default in the future. Given that this changes how WSL behaves when booting up, we wanted to be careful about applying this to user’s already existing WSL distros. ![]() Your WSL instance will stay alive in the same way it did before, which you can read more about here. ![]() Additional modifications had to be made to ensure a clean shutdown (as that shutdown is controlled by systemd now) and to have compatibility with WSLg, It is also important to note that with these change, systemd services will NOT keep your WSL instance alive. Because the WSL init process is responsible for providing the infrastructure for communication between the Linux and Windows components, changing this hierarchy required rethinking some of the assumptions made with the WSL init process. As systemd requires PID 1, the WSL init process started within the Linux distribution becomes a child process of the systemd. ![]() Supporting systemd required changes to the WSL architecture.
0 Comments
Leave a Reply. |