WSL2 Debian Required System D #3304
Assignees
Labels
kind/documentation
Categorizes issue or PR as related to documentation.
Comments
treatmesubj
added
the
kind/documentation
|
/assign @BenTheElder |
|
It would certainly be easier to just suggest users enable systemd. The container ecosystem is largely tested with systemd and we do not have WSL2 CI available #1529. |
|
Thanks for creating this issue and for the link to the "enabling systemd" documentation. |
|
Can you share more about the VM environment, what init is running, what does "docker info" output (eg we want to know about the cgroups) kind has code to ensure this path if not created by the host but I guess even priv container is not getting permission in this environment. |
|
@BenTheElder I disabled systemd again and got the following info. Hope it helps. Debug info |
|
Thanks, I don't understand why this is happening. We should be forcing cgroupns=private with kind v0.20.0+ and therefore I suspect that's a bad assumption versus privileged + hostns and instead we're back to relying on the host systemd to ensure the top level mounts exist and #3277 may be ~the same root cause ...? Unfortunately still not going to get a chance to dig in for a bit and probably not on windows but maybe on alpine |
|
Any news about this? |
|
@syNack0 no, or else there would be a comment here. The maintainers do not use windows. If someone with this issue can upload the logs as per the bug template we can look at those. |
|
(Also nobody has worked on solving the windows CI problem #1529 so we rely entirely on windows-interested contributors) |
|
In #3304 (comment) @BenTheElder wrote:
I stumbled across the following answer in https://stackoverflow.com/a/73376219 by @Domest0s and thought it might be relevant:
|
Ok yeah that is weird, usually you only see that path on a systemd host that has BOTH v1 and v2 mounted ("hybrid" mode; which ... I don't recommend). /sys/fs/cgroup is the normal path in either "unified" (v2) or "legacy" (v1) mode. It's possible that may fix things, are we sure it's not "hybrid" mode systemd though? Or is this the default WSL2 init system (don't know much about that one yet) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be documented:
On WSL2, System D is not enabled by default, but can be easily enabled
Docker doesn't require System D, but KinD relies on it, I guess.
Without System D enabled, KinD serial logs will show
Why is this needed:
KinD has WSL2 docs, but they don't mention this as a an easy fix/requirement
The text was updated successfully, but these errors were encountered: