-
Notifications
You must be signed in to change notification settings - Fork 369
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
CgroupsV2 errors on Fedora 35 with podman #1633
Comments
Does it work if you bind mount |
It helps. I get the node in I am using btrfs with luks encrypted / partition, if that is relevant. Some other k8s distros have currently issues open about that. I did not found any of the symptoms about this in the k0s logs, though. When poking at things, I found
and the containers are not scheduled because of
|
Following https://docs.k0sproject.io/head/troubleshooting/#k0s-will-not-start-on-zfs-based-systems, I see
so the solution should be to somehow get the btrfs snapshotter to be unskipped |
for that, I am adding, as per openshift/microshift#629, kubernetes-sigs/kind#2411
Next, I get in logs
I haven't figured how to deal with that. |
hmm, dunno much about podman but at least when running k0s in Docker you also need some extra cgroups flags if the host is running cgroups v2:
See https://docs.k0sproject.io/head/k0s-in-docker/#1-initiate-k0s |
@jnummelin Thanks, that worked!
So, my command ended up being
the |
@jiridanek glad it worked out. I've added the cgroupns details into the docs too now. |
Before creating an issue, make sure you've checked the following:
Version
v1.23.5+k0s.0
Platform
What happened?
When starting k0s controller using podman, the cluster never finishes starting and I don't get any nodes.
Steps to reproduce
Watch the logs, try to list nodes with
Expected behavior
Node comes up.
Actual behavior
Screenshots and logs
k0spodmanlogs.txt
In a previous run, I saw
Additional context
My issue is similar to #1195.
The text was updated successfully, but these errors were encountered: