In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs.
Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL.
# Test Case
install Ubuntu WSL 24.04 from the MS STore. This version has systemd already enabled.
## Expected Behavior
systemctl status command to work
## Actual Behavior
toor@XPS:~$ systemctl status
Failed to dump process list for 'XPS', ignoring: Input/output error
● XPS
State: degraded
Units: 318 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 1 units
Since: Sat 2022-09-24 08:43:15 PDT; 14min ago
systemd: 251.4-1ubuntu6
Tainted: cgroupsv1
CGroup: /
WSL 24.04 / systemd 255.4-1ubuntu8
* Upstream report: https:/ /github. com/microsoft/ WSL/issues/ 8879 /github. com/systemd/ systemd/ pull/32534 /github. com/systemd/ systemd- stable/ commit/ 8e57759d6d80ef7 72d8e17a4559a67 97e09af93a. patch
* Upstream PR: https:/
* Upstream commit: https:/
In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs.
Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL.
# Test Case
install Ubuntu WSL 24.04 from the MS STore. This version has systemd already enabled.
## Expected Behavior
systemctl status command to work
## Actual Behavior
toor@XPS:~$ systemctl status
Failed to dump process list for 'XPS', ignoring: Input/output error
● XPS
State: degraded
Units: 318 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 1 units
Since: Sat 2022-09-24 08:43:15 PDT; 14min ago
systemd: 251.4-1ubuntu6
Tainted: cgroupsv1
CGroup: /