kind: Kind can't create clusters in F35 with Podman
What happened:
[root@fedora ~]# kind create cluster
enabling experimental podman provider
Creating cluster "kind" ...
β Ensuring node image (kindest/node:v1.23.4) πΌ
β Preparing nodes π¦
ERROR: failed to create cluster: could not find a log line that matches "Reached target .*Multi-User System.*|detected cgroup v1"
What you expected to happen: kind could create a cluster.
How to reproduce it (as minimally and precisely as possible):
- install Fedora 35 server edition
- Install podman 4.0.2
- run kind create cluster
Environment:
- kind version: (use
kind version
):
kind v0.12.0 go1.17.8 linux/amd64
- Kubernetes version: (use
kubectl version
):
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:58:47Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"linux/amd64"}
- Docker version: (use
docker info
): I use podman
Client: Podman Engine
Version: 4.0.2
API Version: 4.0.2
Go Version: go1.16.14
Built: Thu Mar 10 21:26:05 2022
OS/Arch: linux/amd64
- OS (e.g. from
/etc/os-release
):
Fedora release 35 (Thirty Five)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 31 (13 by maintainers)
Same problem happens on macOS Monterey (v12) with Apple M1:
For me it looks a resource issue. I am going to close it as with more resource I can achieve what I need.
Itβs working for me now using another method I use podman machine. I can create clusters with single and multiple nodes.
@jrmanes this issue is about podman and fedora, that seems to be a problem in the kernel. The one you are reported seems related to https://github.com/kubernetes-sigs/kind/issues/2718 , because you are using docker on mac with ARM architecture, please check if the environment variable is your problem as described in the linked issue.
Could you try the latest kernel 5.16.17-200.fc35? I donβt see any issue with this kernel.
my
podman info
Nope, it seems not connected to the kernel, I have tested again a fresh install F35 and skipped any update.
And still geting the same error