Pi-Hole update deadlock (Docker-DNS)

[BernhardMillauerAdventics]

This is not a issue report but a help to get out of a dns service deadlock.

I noticed an issue with coolify/docker when the self-hosted pi-hole is used as DNS server.
The issue emerges when you do a "Pull Latest Images & Restart" on the pi-hole service to rigger the update.
The service shuts down, so does the DNS service, and then docker tries to resolve and pull the latest pi-hole image from docker-hub (or wherever you get it from). Because the DNS service is unreachable, no image can be pulled and pi-hole doesn't start up anymore.

In this case your only bet is to set the dns server

• debian: update /etc/resolv.conf

  # priority calling, based on availability
  search lan
  nameserver 192.168.1.4 # local host
  nameserver 1.1.1.1 # global dns
  

and try to start the service again.

I hope this help people to avoid this deadlock situation.

To the coolify devs: wouldn't it be better to do a "docker compose pull && docker compose up" instead killing the server and and docker compose up --force?