-
Notifications
You must be signed in to change notification settings - Fork 42
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
[BUG] svclb-traefik* won't start after host crash and restart. #34
Comments
|
I get the same error after creating a new cluster with k3d. My host OS is RHEL 8.5. I think it is related to the fact that RHEL 8.5 only supports nftables, but the kilpper-lb docker image has iptables symlinked to the legacy version. Relevant versions of things:
My workaround was to recreate the rancher/klipper-lb:vb0.3.4 image with this Dockerfile:
Then I used It's a hack, but it gets ingress working on my system. |
Check this out for a quick fix: To solve the problem properly (rather than use this ad-hoc fix), I would suggest rewriting check_iptables_mode() to use grep inside of the /sbin directory, rather than trying to use lsmod / modprobe |
It has been now over a year and this issue has still not been fixed? There is more and more nft-based systems and this is really annoying... In particular, with 0.4.3:
This is current (5.5.1) k3d using klipper-lb:v0.4.3 on Oracle Linux Server 8.7 (RHEL 8.7 binary compatible). proposed change do the detection would be to replace
|
What did you do
How was the cluster created?
What did you do afterwards?
My host crashed and after restarting it and restarting k3d, I am no longer able to connect to any app service through ingress.
What did you expect to happen
Ingress should work
Screenshots or terminal output
Which OS & Architecture
Linux rockylinux8.linuxvmimages.local 4.18.0-348.20.1.el8_5.x86_64 #1 SMP Thu Mar 10 20:59:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Which version of
k3d
k3d version
Which version of docker
docker version
anddocker info
[rockylinux@rockylinux8 infra_k3d]$ docker info
The text was updated successfully, but these errors were encountered: