You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Podman provider fails to create a cluster running rootless on Fedora 41. This may only impact developers whose machines upgraded to Fedora 41 from Fedora 40 or earlier.
Note to community - this is more of a public service announcement than actual bug. Root cause is at the podman/Fedora level.
Error:
Command Output: Error: netavark: nftables error: unable to execute nft: No such file or directory (os error 2)
What you expected to happen:
KinD is able to create the cluster
How to reproduce it (as minimally and precisely as possible):
Upgrade host from Fedora 40 to Fedora 41 (if this happens on a clean Fedora 41 install, there is a much larger regression in Fedora).
I see the bug was solved so I think we can close this
It seems it was some environmtal issue
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
What happened:
Podman provider fails to create a cluster running rootless on Fedora 41. This may only impact developers whose machines upgraded to Fedora 41 from Fedora 40 or earlier.
Note to community - this is more of a public service announcement than actual bug. Root cause is at the podman/Fedora level.
Error:
What you expected to happen:
KinD is able to create the cluster
How to reproduce it (as minimally and precisely as possible):
kind
Anything else we need to know?:
Related Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2331672
Environment:
kind version
):kind v0.25.0 go1.23.3 linux/amd64
docker info
,podman info
ornerdctl info
):Client: Podman Engine
Version: 5.3.1
API Version: 5.3.1
Go Version: go1.23.3
Built: Wed Nov 20 19:00:00 2024
OS/Arch: linux/amd64
/etc/os-release
): Fedora 41kubectl version
):The text was updated successfully, but these errors were encountered: