ErrImagePull on Kubernetes when trying to deploy

I am completely new to Kubernetes so please bare with me. I'm trying to deploy and im getting the below error on 2 pods.

I've extracted out the below from kubectl describe pod my-retool-5cc6548b56-gvfcx. I've tried '3.52.7-stable' and 'latest'

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  73s                default-scheduler  Successfully assigned default/my-retool-5cc6548b56-gvfcx to k8s-node-1
  Warning  Failed     53s                kubelet            Failed to pull image "tryretool/backend:3.52.7-stable": failed to pull and unpack image "docker.io/tryretool/backend:3.52.7-stable": failed to resolve reference "docker.io/tryretool/backend:3.52.7-stable": failed to do request: Head "https://registry-1.docker.io/v2/tryretool/backend/manifests/3.52.7-stable": dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: read udp 127.0.0.1:35710->127.0.0.53:53: i/o timeout
  Normal   Pulling    38s (x2 over 73s)  kubelet            Pulling image "tryretool/backend:3.52.7-stable"
  Warning  Failed     22s (x2 over 53s)  kubelet            Error: ErrImagePull
  Warning  Failed     22s                kubelet            Failed to pull image "tryretool/backend:3.52.7-stable": failed to pull and unpack image "docker.io/tryretool/backend:3.52.7-stable": failed to resolve reference "docker.io/tryretool/backend:3.52.7-stable": failed to do request: Head "https://registry-1.docker.io/v2/tryretool/backend/manifests/3.52.7-stable": dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: read udp 127.0.0.1:36400->127.0.0.53:53: i/o timeout
  Normal   BackOff    10s (x2 over 53s)  kubelet            Back-off pulling image "tryretool/backend:3.52.7-stable"
  Warning  Failed     10s (x2 over 53s)  kubelet            Error: ImagePullBackOff

Hi @rcanpolat,

Thanks for reaching out & apologies for the delay here. I see a more recent thread where you are working on your deployment. Are you still seeing this "failed to pull image" error?