-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Install fails due to missing cgroup (v2) #219
Comments
It's called out here: https://docs.k3s.io/advanced#raspberry-pi |
Modified: roles/raspberrypi/tasks/main.yml
I would do a PR, but I don't have privileges... |
I've just hit this, too. It's fixed in #185 but it's been waiting to be merged for over a year 😞 It seems this project is dead. |
I experienced this issue yesterday installing on my Turing Pi V2 cluster. I noted that it's in the configuration but it didn't work. I manually added the configuration as the fastest way to resolve the issue. One other thing... the last instruction in README.md didn't make sense to me. kube.cfg was copied by Ansible to the master node. What didn't make sense to me was the difference between source and target. As written, wouldn't that copy in the same folder? I didn't do that step. Haven't deployed any containers yet but kubectl get nodes sees all my nodes just fine. |
Resolved with #151 |
I have 4 brand new Raspberry Pi CM4s, running 64 bit Raspberry Pi OS Lite (no GUI), on the nodes, and with GUI on the master.
all 4 failed to start the service:
level=fatal msg="failed to find memory cgroup (v2)"
Your documentation should provide this as a pre-req, or add this code to your
prereq/tasks/main.yml
file:The text was updated successfully, but these errors were encountered: