Hazem Hemied

I did, and here is the output ```bash [root@fedora ~]# kind create cluster --image kindest/node:v1.23.4@sha256:0e34f0d0fd448aa2f2819cfd74e99fe5793a6e4938b328f657c8e3f81ee0dfb9 enabling experimental podman provider Creating cluster "kind" ... ✓ Ensuring node image (kindest/node:v1.23.4) 🖼 ✗...

``` [root@fedora ~]# kind create cluster --image kindest/node:v1.23.4@sha256:0e34f0d0fd448aa2f2819cfd74e99fe5793a6e4938b328f657c8e3f81ee0dfb9 -v 7 enabling experimental podman provider Creating cluster "kind" ... DEBUG: podman/images.go:58] Image: docker.io/kindest/node@sha256:0e34f0d0fd448aa2f2819cfd74e99fe5793a6e4938b328f657c8e3f81ee0dfb9 present locally ✓ Ensuring node image (kindest/node:v1.23.4) 🖼...

You are right, my bad. ```bash [root@fedora ~]# podman info host: arch: amd64 buildahVersion: 1.24.1 cgroupControllers: - cpuset - cpu - io - memory - hugetlb - pids - misc...

Here is the logs folder [3808958841.zip](https://github.com/kubernetes-sigs/kind/files/8334841/3808958841.zip)

Nothing suspicious, actually it is clean install to test kind with podman 4 Additional info ```bash [root@fedora ~]# podman network ls NETWORK ID NAME DRIVER faed16303522 kind bridge 2f259bab93aa podman...

Nope, it seems not connected to the kernel, I have tested again a fresh install F35 and skipped any update. - Kernel ``` 5.14.10-300.fc35.x86_64 ``` - Podman version ``` Version:...

Here is the output if I remove Podman and install Docker ```bash kind create cluster Creating cluster "kind" ... ✓ Ensuring node image (kindest/node:v1.23.4) 🖼 ✓ Preparing nodes 📦 ✓...

Unfortunately, the issue still remains. I tested with the latest kernel and latest version.

The issue still exist, In my current setup, ```bash ➜ kind create cluster --name test --config cluster-ha-demo.yaml using podman due to KIND_EXPERIMENTAL_PROVIDER enabling experimental podman provider Creating cluster "test" ......

It's working for me now using another method I use podman machine. I can create clusters with single and multiple nodes.