Unable to resolve any domains

[plc0]

my pihole is running via portainer on a raspberry pi 4. even when I ssh into the container, I get a resolution error:

sudo docker exec -it pihole /bin/bash
sudo: unable to resolve host pitron: Name or service not known
root@pihole:/#

but I can then attach successfully to the container.

this is the output of pihole -debug: gist:91e673652558ba0fef198a9f9f9b029a · GitHub

it says:

172.17.0.3/16 does not match the IP found in /etc/pihole/setupVars.conf

in that file it says:

IPV4_ADDRESS=0.0.0.0

and whenever I update it with 172.17.0.3 it gets overwritten back to 0.0.0.0?

if I run dig ns1.pi-hole.net:

root@pihole:/# dig ns1.pi-hole.net

;; reply from unexpected source: 172.17.0.1#53, expected 192.168.7.8#53

and yet using @8.8.8.8 works fine:

root@pihole:/# dig ns1.pi-hole.net @8.8.8.8

; <<>> DiG 9.10.3-P4-Debian <<>> ns1.pi-hole.net @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30871
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:
;ns1.pi-hole.net. IN A

;; ANSWER SECTION:
ns1.pi-hole.net. 3599 IN A 185.136.96.96

;; Query time: 147 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Oct 05 04:04:06 UTC 2020
;; MSG SIZE rcvd: 60

any help would be much appreciated!!!

[Bucking_Horn]

(For your own privacy and security, please do not post your full, unsanitised debug log output. When providing a debug token, please post just the token that is shown once the debug finishes, preferably by copy and paste.)

Your issues are likely related to correctly configuring Docker's network driver.

Also, you are trying to tamper with the Docker image in ways not advisable, e.g. by running updates on your Pi-hole or its OS from within the container:

E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
root@pihole:/# sudo !!
sudo apt-get update

Note that any such changes you apply to a container would not survive a container restart.

In addition, you seem to have altered some of Pi-hole's default web server's configurations:

*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 4066 Oct  5 03:57 /etc/lighttpd/lighttpd.conf
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"' 2>/dev/null"

I doesn't seem you are using Pi-hole's official Docker image at all?

[DanSchaper]

@plc0

sudo: unable to resolve host pitron: Name or service not known

That's a warning from sudo, it doesn't actually stop or break anything. sudo tries to look up the host name since you can have per host sudo rules. Easy solution to that is to put pitron in your /etc/hosts file with localhost as the address.