# awx execution environment in kubernetes using private registry host not found

**URL:** <https://forum.ansible.com/t/awx-execution-environment-in-kubernetes-using-private-registry-host-not-found/36372>\
**Category:** AWX Project\
**Tags:** awx, ee, kubernetes\
**Created:** [February 26, 2022, 5:07am UTC](https://forum.ansible.com/t/awx-execution-environment-in-kubernetes-using-private-registry-host-not-found/36372 "2022-02-26T05:07:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![suppaduppax](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@suppaduppax](https://forum.ansible.com/u/suppaduppax)\
**Post date:** [February 26, 2022, 5:07am UTC](https://forum.ansible.com/t/awx-execution-environment-in-kubernetes-using-private-registry-host-not-found/36372/1 "2022-02-26T05:07:04Z")

</div>

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](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!

---

<div class="post-metadata">

**Author:** ![Vincent\_Rubiolo](https://avatars.discourse-cdn.com/v4/letter/v/a183cd/32.png) [@Vincent\_Rubiolo](https://forum.ansible.com/u/Vincent_Rubiolo)\
**Post date:** [February 28, 2022, 9:41am UTC](https://forum.ansible.com/t/awx-execution-environment-in-kubernetes-using-private-registry-host-not-found/36372/2 "2022-02-28T09:41:10Z")

</div>

Hi there,

Do you get the same error if you do the ping within a playbook running in AWX (and not just a commandline shell in the container)?

Let us know how it goes,

Vincent
