Pihole on Docker - DNS resolution is currently unavailable error

Ripcord · 5. Oktober 2019

I once was able to install and use PiHole on Raspberry Pi on OMV via Docker. I moved to Rock64 board. I am using OpenMediaVault and using Docker inside it. I installed PiHole and configured it and have the following issue.Would be really great it someone help me out here.

Current setup:
Rock64 board running OpenMediaVault. Docker is running inside OMV
IP of Omv: 192.168.178.24
IP of PiHole: 192.168.178.100
Current log:

Code

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying...
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing...
 ::: Starting docker specific checks & setup for docker pihole/pihole


WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11)


search fritz.box


nameserver 127.0.0.11
options ndots:0
  [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u5
  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [i] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf...[K  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
::: Pre existing WEBPASSWORD found
Using custom DNS servers: 127.0.0.1 & 1.1.1.1
DNSMasq binding to default interface: eth0
Added ENV to php:
"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
"ServerIP" => "192.168.178.100",
"VIRTUAL_HOST" => "192.168.178.100",
Using IPv4


::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))


https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts


https://mirror1.malwaredomains.com/files/justdomains


http://sysctl.org/cameleon/hosts


https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt


https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt


https://hosts-file.net/ad_servers.txt


::: Testing pihole-FTL DNS: FTL started!


::: Testing lighttpd config: Syntax OK


::: All config checks passed, cleared for startup ...


 ::: Docker start setup complete


  [i] Pi-hole blocking is enabled


  [✗] DNS resolution is currently unavailable
....
 [i] Time until retry: 5[K  [i] Time until retry: 4[K  [i] Time until retry: 3[K  [i] Time until retry: 2[K  [i] Time until retry: 1[K  [✗] DNS resolution is not available

Alles anzeigen

I use the below docker arguments:
-p 53:53/tcp -p 53:53/udp -p 67:67/udp -p 80:80/tcp -p 443:443/tcp --dns 127.0.0.1 --dns 1.1.1.1 --cap-add NET_ADMIN

raulfg3 · 5. Oktober 2019

revise that you install on a macvlan not in a bridge LAN

Ripcord · 5. Oktober 2019

In this case what should I provide for Host IP & ports?

Morlan · 5. Oktober 2019

https://forum.openmediavault.o…-Unbound-a-Recursive-DNS/

Ripcord · 5. Oktober 2019

I was following this exact guide. After this only I get the error I posted.

Ripcord · 6. Oktober 2019

with my limited knowledge on Docker and networking, I think I have hit a pot hole

raulfg3 · 6. Oktober 2019

use variables instead of arguments

tinh_x7 · 29. Dezember 2019

Hi,

I have similar issue, how do you fix it ?

Code

https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt,
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt,
https://hosts-file.net/ad_servers.txt,
sudo: unable to stat /etc/sudoers: Permission denied,
sudo: no valid sudoers sources found, quitting,
sudo: unable to initialize policy plugin,
::: Testing pihole-FTL DNS: [cont-init.d] 20-start.sh: exited 1.,
[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] syncing disks.,
[s6-finish] sending all processes the TERM signal.,
[s6-finish] sending all processes the KILL signal and exiting.,
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] 01-resolver-resolv: applying... ,
[fix-attrs.d] 01-resolver-resolv: exited 0.,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] 20-start.sh: executing... ,
 ::: Starting docker specific checks & setup for docker pihole/pihole,
WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server,
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11),
,
nameserver 127.0.0.11,
options ndots:0,
  [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u5,
,
  [i] Installing configs from /etc/.pihole...,
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!,
  [i] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf...
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf,
chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory,
::: Pre existing WEBPASSWORD found,
Using custom DNS servers: 127.0.0.1 & 8.8.8.8,
DNSMasq binding to custom interface: bond0,
Added ENV to php:,
			"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",,
			"ServerIP" => "192.168.1.80",,
			"VIRTUAL_HOST" => "192.168.1.80",,
Using IPv4 and IPv6,
::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)),
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts,
https://mirror1.malwaredomains.com/files/justdomains,
http://sysctl.org/cameleon/hosts,
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt,
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt,
https://hosts-file.net/ad_servers.txt,
sudo: unable to stat /etc/sudoers: Permission denied,
sudo: no valid sudoers sources found, quitting,
sudo: unable to initialize policy plugin,
::: Testing pihole-FTL DNS: [cont-init.d] 20-start.sh: exited 1.,
[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] syncing disks.,
[s6-finish] sending all processes the TERM signal.,
[s6-finish] sending all processes the KILL signal and exiting.,
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] 01-resolver-resolv: applying... ,
[fix-attrs.d] 01-resolver-resolv: exited 0.,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] 20-start.sh: executing... ,
 ::: Starting docker specific checks & setup for docker pihole/pihole,
WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server,
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11),
,
nameserver 127.0.0.11,
options ndots:0,
  [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u5,
,
  [i] Installing configs from /etc/.pihole...,
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!,
  [i] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf...
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf,
chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory,
::: Pre existing WEBPASSWORD found,
Using custom DNS servers: 127.0.0.1 & 8.8.8.8,
DNSMasq binding to custom interface: bond0,
Added ENV to php:,
			"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",,
			"ServerIP" => "192.168.1.80",,
			"VIRTUAL_HOST" => "192.168.1.80",,
Using IPv4 and IPv6,
::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)),
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts,
https://mirror1.malwaredomains.com/files/justdomains,
http://sysctl.org/cameleon/hosts,
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt,
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt,
https://hosts-file.net/ad_servers.txt,
sudo: unable to stat /etc/sudoers: Permission denied,
sudo: no valid sudoers sources found, quitting,
sudo: unable to initialize policy plugin,
::: Testing pihole-FTL DNS: [cont-init.d] 20-start.sh: exited 1.,
[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] syncing disks.,
[s6-finish] sending all processes the TERM signal.,
[s6-finish] sending all processes the KILL signal and exiting.,

Alles anzeigen

raulfg3 · 30. Dezember 2019

As I say on October use variables instead of arguments

But for your log, perhaps your problem are not DNS, I suspect that you do not have enought permission:

sudo: unable to stat /etc/sudoers: Permission denied,
sudo: no valid sudoers sources found, quitting,
sudo: unable to initialize policy plugin,

tinh_x7 · 30. Dezember 2019

I did used variables.
I tried to added Dockeruser in the env variables, but it still encountered errors.

There are two files in pihole that keep changed itself ownership to ‘openmediavault-gui’.

Code

total 40
drwxr-xr-x+  3 openmediavault-webgui openmediavault-config 4096 Jan  2 17:20 .
drwx--x--x+ 18 root                  root                  4096 Jan  2 17:13 ..
-rw-rw----+  1 root                  root                   313 Jan  2 17:20 adlists.list
-rw-rw----+  1 root                  root                   596 Jan  2 17:20 dns-servers.conf
drwxrwx--x+  2 root                  root                  4096 Jan  2 17:20 dnsmasq.d
-rw-rw----+  1 root                  root                    20 Jan  2 17:20 localbranches
-rw-rw----+  1 root                  root                    42 Jan  2 17:20 localversions
-rw-r--r--   1 openmediavault-webgui openmediavault-config    0 Jan  2 17:20 pihole-FTL.conf
-rwxrwxrwx   1 openmediavault-webgui openmediavault-config    0 Jan  2 17:20 regex.list
-rw-rw----+  1 root                  root                   409 Jan  2 17:20 setupVars.conf
-rw-rw----+  1 root                  root                   409 Jan  2 17:20 setupVars.conf.update.bak

Alles anzeigen

apveening · 31. Dezember 2019

Something changed around October, there are some Docker updates I can't implement without the Pihole container becoming unstable. I've been testing various configurations (OMV4, OMV5 and OMV5 with Proxmox) in virtual machines and in none I can get the Pihole container to run stable. As long as that remains so, I won't update Docker on my Raspberry Pi 3B+ again as I am getting tired of flashing back the previous installation (daily images).

Jetzt mitmachen!