rapid-tailor-25200
09/18/2023, 2:25 PM$ netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 :::8443 :::* LISTEN 1/qemu-x86_64
With docker runtime (UI loads fine)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 1/qemu-x86_64
The ports are reachable outside the container. When I do a wget from a different container the netstat shows tcp connection ESTABLISHED. But manager 8443 port doesnt seem to be responding properly. kubectl portforwarding exists as soon as a connection attempt is made.
I'm sure I'm missing something very simple but I've been looking in the docs and could not find any config change other than volume mount.
Have any one seen this? Any lead or suggestion would be helpful.
Thanks
here too.
-- Works file when the docker runtime is selected.
-- UI doesn't load when k3s containerd is selected (all pods up and running.)
Only difference I could find is that the port is bound to ipv4 in case of docker runtime. While it is bound to both in case of containerd setup (same for both rancher and EKS setups).
I'm sure I'm missing something very simple but I've been looking in the docs and could not find any config change other than volume mount.
Have any one seen this? Any lead or suggestion would be helpful.
Thanks!acoustic-sugar-94270
09/20/2023, 1:30 PMrapid-tailor-25200
09/20/2023, 3:14 PMTo test this I installed rancher desktop. And reproduced the same behavior by changing container run time through settings and deploying through helm (by selecting appropriate run time).
Basically i was using helm. The only change is overriding the containerd part True in the Values.