https://rancher.com/ logo
Join Slack
Powered by
I've been getting issues with networking via servi...
# rancher-desktop
v
I've been getting issues with networking via services for Rancher Desktop Kubernetes on Windows, and have narrowed it down to this log:
Copy code
E0606 16:04:11.939497     822 proxier.go:1564] "Failed to execute iptables-restore" err=<
	exit status 4: Warning: Extension recent revision 0 not supported, missing kernel module?
	Warning: Extension recent is not supported, missing kernel module?
	Warning: Extension recent is not supported, missing kernel module?
	Warning: Extension recent is not supported, missing kernel module?
	Warning: Extension recent is not supported, missing kernel module?
	Warning: Extension recent is not supported, missing kernel module?
	iptables-restore v1.8.11 (nf_tables): 
	line 92: RULE_APPEND failed (No such file or directory): rule in chain KUBE-SVC-LGXKL4DPQOC3NS43
	line 93: RULE_APPEND failed (No such file or directory): rule in chain KUBE-SVC-LGXKL4DPQOC3NS43
	line 96: RULE_APPEND failed (No such file or directory): rule in chain KUBE-SVL-LGXKL4DPQOC3NS43
	line 97: RULE_APPEND failed (No such file or directory): rule in chain KUBE-SVL-LGXKL4DPQOC3NS43
	line 101: RULE_APPEND failed (No such file or directory): rule in chain KUBE-SEP-P7AKUFAGM2VB6I5P
	line 103: RULE_APPEND failed (No such file or directory): rule in chain KUBE-SEP-FC4SGCPEDEJXJOEW
 >
Any suggestions on how to further troubleshoot? (More details in 🧵~)~ Edit: 
wsl --update
fixed it!
Copy code
Version: 1.19.1
Network status: online 
Kubernetes: 1.32.5
CE: moby
Windows 11 I have done a "Reset Kubernetes" as well as a 
wsl --shutdown
after shutting down rancher desktop (I had the symptoms with an older version of everything earlier, but only now have a clue of whats going wrong)
Empirically the problem I'm facing is that sometimes communications work via services, and sometimes not. My pods can always communicate via pod IPs. My theory is that something is going wrong with creating iptables
(more full log incoming)
Here's a bigger log around it. At 16:12 I deleted the service 
worldserver-mux-0
in an attempt to get kubernetes to recreate the network routes
deleted-worldserver-mux-0-which-others-could-not-talk-to.txt
WSL update fixed it
Copy code
wsl --version
WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.4061
> wsl --update
Checking for updates.
Updating Windows Subsystem for Linux to version: 2.5.7.
It seems like there is some sort of hidden compatibility on a new(er) 
wsl
version. May I suggest adding some sort of check in Rancher Desktop?
f
Sounds like a good idea. I also find 2.5.7 more stable than older releases. I've file Add a diagnostics for wsl version · Issue #8756
🎉 1
4 Views
Open in Slack
PreviousNext
Powered by