Hello, I have a possibly dumb question. I have k3d running on a coder instance at my company. K3d is able to come up but im seeing all the kube-system pods fail to pull images and are stuck in container creating, showing : error:

dial tcp: lookup <http://registry-1.docker.io|registry-1.docker.io>: Try again.

If i start he k3d cluster with coreDNS disabled tho, the pods are able to come up and ull their images. I tried mounting my coder instance resolv.conf into the k3d server thinking that might help and also adjusted my coredns cm to forward to the nameserver in my code instance resolv.conf after that, but im having no luck. I obv dont want to disable coredns, but its weird that works if I disable it, the only thing I can think of is that being INSIDE a coder instance is kind of doing some docker/kuberenets inception