This message was deleted.
# k3da
adamant-kite-43734
04/18/2025, 3:22 PMThis message was deleted.
w
wide-garage-9465
04/18/2025, 4:28 PMHey!
Likely firewalld or ufw blocking?
w
witty-zebra-93264
04/21/2025, 11:35 AMFirewalld was disabled and so was selinux
witty-zebra-93264
04/21/2025, 11:54 AMI repeated the same steps multiple times over the weekend on Rocky and Redhat. Rocky works every time and Redhat fails with the above errors every time. They're a 1:1 so I assumed what works of Rocky would work on RHEL. That does not seem to be the case. I would have hoped there would have been some sort of mention in the FAQ or something. I think there is a 2 year old open ticket on github issues that might be related..
witty-zebra-93264
04/21/2025, 4:33 PMI also disabled FIPS as well just in case. Still no luck
witty-zebra-93264
04/21/2025, 4:35 PMI had partial luck with a rootless approach but have to make all sorts of modifications just to end up with permission denied errors related to /proc or something
w
wide-garage-9465
04/21/2025, 4:45 PMI never got to test it on RHEL, so I really have no clue.
You're running a single node setup and the k3d cluster create command succeeds?
What are the versions? (OS, Docker, k3d, K3s)
w
witty-zebra-93264
04/21/2025, 4:59 PMrhel 8.10 with rootful podman k3d is 5.7.4 but had same issue on latest. Using default k3s version
witty-zebra-93264
04/21/2025, 4:59 PMI got it working with docker as root. Will try a rootless docker setup now. Maybe podman support is to oexperimental.
👍 1
w
wide-garage-9465
04/21/2025, 5:02 PMThere is no real podman support. It's just as good as the docker API compatibility of podman.
21 Views