I’m running the usual setup:
sudo ./k3s server
part of the last loglines:
-A KUBE-POD-FW-UB5SIFWB2MWAWWKN -m comment --comment “rule to log dropped traffic POD name:coredns-85cb69466-jlnsb namespace: kube-system” -m mark ! --mark 0x10000/0x10000 -j NFLOG --nflog-group 100 -m limit --limit 10/minute --limit-burst 10
-A KUBE-POD-FW-UB5SIFWB2MWAWWKN -m comment --comment “rule to REJECT traffic destined for POD name:coredns-85cb69466-jlnsb namespace: kube-system” -m mark ! --mark 0x10000/0x10000 -j REJECT
-A KUBE-POD-FW-UB5SIFWB2MWAWWKN -j MARK --set-mark 0/0x10000
-A KUBE-POD-FW-UB5SIFWB2MWAWWKN -m comment --comment “set mark to ACCEPT traffic that comply to network policies” -j MARK --set-mark 0x20000/0x20000
COMMIT
W1108 12:03:57.936760 4296 sysinfo.go:203] Nodes topology is not available, providing CPU topology
E1108 12:04:01.507228 4296 proxier.go:1638] “Failed to execute iptables-restore” err=“exit status 1 (ip6tables-restore: line 21 failed\n)”
Is k3s not able to run on WSL?