It appears to be a known issue that WSL1 does not support F_OFD_SETLKW, which is what systemd is using here. I could add a fallback to use F_SETLKW instead, but according to [1], it sounds like the locking is just broken on WSL1? So the "fallback" would probably lead to even more issues.
Do you get the same error in the "WSL2 and systemd disabled" case? I don't understand why disabling systemd would change anything related to the kernel. [1] https://github.com/Microsoft/WSL/issues/1927 ** Bug watch added: github.com/Microsoft/WSL/issues #1927 https://github.com/Microsoft/WSL/issues/1927 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080257 Title: [WSL] systemd fails to upgrade on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2080257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
