Single node k3s - connect to guest host in Fleet - DNS issue

k3s, k3OS, and k3d
1

For testing purposes, I started a Docker single node Rancher container and now I want to connect Fleet to my git repo via git protocol (git://), which is running as daemon on my local machine.
Is there a special name I have to use to connect to the guest host? When I try my computer name, Rancher tells me that it’s unable to look it up, so I guess DNS resolution is not working:
Git ls-remote git://my-pc-name/fleet refs/heads/main error: exit status 128, detail: fatal: unable to look up my-pc-name (port 9418) (Try again)
When trying with the IP 192.168.13.160 (found via kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup my-pc-name), it’s working.
Thanks!

1 Like
2

I have observed the same thing in my rancher deployment at home and at work. At home I got by it by directing the git-repo to my local gitlab server by IP address. This resolved both the DNS “hiccups” and the rate limit errors I was receiving. At work we constantly have DNS “hiccups” as the AD DCs sync. I’d love to know how to modify the retry frequency to keep this from happening.