Closed daurnimator closed 2 years ago
Version (k3OS / kernel)
k3os version v0.20.7-k3s1r0
5.4.0-73-generic rancher/k3os#82 SMP Thu Jun 3 02:29:43 UTC 2021
Architecture
x86_64
Describe the bug
My network has both ipv4 and ipv6 connectivity; however k3os seems to pick up ipv6 first, and ignores ipv4:
I0830 17:33:25.632389 3857 node.go:172] Successfully retrieved node IP: 1234::1234 I0830 17:33:25.632482 3857 server_others.go:140] kube-proxy node IP is an IPv6 address (1234::1234), assume IPv6 operation I0830 17:33:25.643111 3857 server_others.go:186] Using iptables Proxier. F0830 17:33:25.643200 3857 server.go:495] unable to create proxier: CIDR 10.42.0.0/16 has incorrect IP version: expect isIPv6=true
To Reproduce
Expected behavior
Actual behavior
Additional context
Turning off ipv6 (sudo connman config myethernetdevice ipv6 off) allows k3s to boot.
sudo connman config myethernetdevice ipv6 off
this should be a decent workaround in your system config:
boot_cmd: - connman config myethernetdevice ipv6 off
Version (k3OS / kernel)
k3os version v0.20.7-k3s1r0
5.4.0-73-generic rancher/k3os#82 SMP Thu Jun 3 02:29:43 UTC 2021
Architecture
x86_64
Describe the bug
My network has both ipv4 and ipv6 connectivity; however k3os seems to pick up ipv6 first, and ignores ipv4:
To Reproduce
Expected behavior
Actual behavior
Additional context
Turning off ipv6 (
sudo connman config myethernetdevice ipv6 off
) allows k3s to boot.