few-night-4597204/18/2023, 6:25 PM
When I look at the docker logs for the server node, its crapping out on:
DEBU Waiting for node k3d-dc3-server-0 to get ready (Log: 'k3s is up and running')
Thoughts? I'm not coming up with a whole lot when googling 😞
time="2023-04-18T18:11:05Z" level=info msg="Run: k3s kubectl" time="2023-04-18T18:11:05Z" level=fatal msg="failed to find cpu cgroup (v2)"
How would I go about adding this in k3d? Since k3d is abstracting k3s?
K3S needs cgroups to start the systemd service. cgroups can be enabled by appending cgroup_memory=1 cgroup_enable=memory to /boot/cmdline.txt
from https://stackoverflow.com/questions/73021599/how-to-enable-cgroup-v2-in-wsl2 I don't really understand exactly what I just did and if it's going to break something else. Didn't have to do this yesterday or for the last months on win11 or win10
[wsl2] kernelCommandLine = cgroup_no_v1=all