I can’t seem to troubleshoot why my private registry under harbor.k3s.home/awx/awx-ee-homelab:latest is throwing this error:
49s Warning Failed pod/automation-job-326-jmqsg Failed to pull image “harbor.k3s.home/awx/awx-ee-homelab:latest”: rpc error: code = Unknown desc = failed to pull and unpack image “harbor.k3s.home/awx/awx-ee-homelab:latest”: failed to resolve reference “harbor.k3s.home/awx/awx-ee-homelab:latest”: failed to do request: Head “https://harbor.k3s.home/v2/awx/awx-ee-homelab/manifests/latest”: dial tcp: lookup harbor.k3s.home: no such host
I’ve exec’d into awx-task and awx-web and I can ping harbor.k3s.home no problem, so I’m at a loss. Why isn’t harbor.k3s.home resolving properly in my job_template?
$ kubectl exec awx-86c65f449f-xnd6w -c awx-task -it – /bin/bash
bash-4.4$ ping -c 3 harbor.k3s.home
PING harbor.k3s.home (192.168.0.245) 56(84) bytes of data.
64 bytes from k3s-lb.home (192.168.0.245): icmp_seq=1 ttl=63 time=0.401 ms
64 bytes from k3s-lb.home (192.168.0.245): icmp_seq=2 ttl=63 time=0.487 ms
64 bytes from k3s-lb.home (192.168.0.245): icmp_seq=3 ttl=63 time=0.685 ms
— harbor.k3s.home ping statistics —
rtt min/avg/max/mdev = 0.401/0.524/0.685/0.120 m
I’ve tried adding a coredns configmap to force the dns (192.168.0.1) but that didn’t work…
:53 {
errors
health
ready
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
}
hosts /etc/coredns/NodeHosts {
ttl 60
reload 15s
fallthrough
}
prometheus :9153
forward . 192.168.0.1 # ← force to use specific dns ??
cache 30
loop
reload
loadbalance
}
If anyone has any ideas let me know. Thanks!