[Support] devzwf - pihole DoT/DoH

[ZappyZap]

This repo was created to update the  piHole DoT/DoH by flippinturt
https://forums.unraid.net/topic/101615-support-depreciated-flippinturt-pihole-dot-doh/

 

Official pihole docker with added DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH).

• DoH uses cloudflare (1.1.1.1/1.0.0.1) and DoT uses google (8.8.8.8/8.8.4.4). Config files are exposed so you can modify them as you wish e.g. to add more services.

Application:  https://hub.docker.com/r/devzwf/pihole-dot-doh

 

Make sure to look at the complete documentation

 

Please make sure you set a static IP for this docker, as DHCP will not work!

FAQ:
Q: Can this be installed on top of flippinturt's current pihole DoT-DoH?
A: Yes, this can be installed over, without any problems

Q: How do I change the hostname?
A: Use the '--hostname namehere' parameter, under 'extra parameters' in the containers settings

 

Please post any questions/issues relating to this template you have in this thread.

Edited December 7, 2022 by ZappyZap

[ZappyZap]

Reserved

[waxwing]

Ah thank you for this!

I've installed it over my existing flippinTurt container as suggested and it's working well.

[luckyheiko]

hello

 

is ist possible to set the (time)

/etc/cron.d#   pihole gravity job // 22 1   * * 7   root    PATH="$PATH:/usr/

more random?

 

and maybe also the updatechecker?

 

thanks in advance

[ZappyZap]

I do not touch this part 
i am building on top of pihole official container who is setting this.

perhaps better place to request this is : https://github.com/pi-hole/docker-pi-hole
but i am fairly positive it is already random
 

# Pi-hole: Update the ad sources once a week on Sunday at a random time in the
#          early morning.

 

Edited December 8, 2022 by ZappyZap

[Bleak]

When doing a clean install your template is empty at the following places

 

You need to fill this to be able to create the docker and without these filled there will not be a appdata directory for this docker. I filled this with:

/mnt/user/appdata/pihole-dot-doh/pihole/

/mnt/user/appdata/pihole-dot-doh/dnsmasq.d/

/mnt/user/appdata/pihole-dot-doh/config/

(copied from the original outdated testdasi template)

 

Maybe you can fill these in the template with the above?

Makes it a little easier to install for the first time .

Spoiler

especially for people that are not that versed in docker templates and then just create a directory for pihole in the appdata directory but because then the permissions are wrong no config files are created and nothing works and start hating yourself cause your household has now not had dns for an hour and are getting angry at you...

 

Yes I am stupid... But happy with the config files and my stubby is no longer set to google.

 

EDIT:

Thank you for keeping this docker alive in unraid!

Edited December 21, 2022 by Bleak

[ZappyZap]

Hi,

The best practice i think is to leave those empty and let the user fill it
perhaps @Squid can let me know if i am wrong or not.

 

[Squid]

/config container paths are automatically mapped to whatever the user sets in Settings - Docker for the default appdata path.  In your case there was a minor bug in dockerMan which prevented it from doing /config/ and it only did /config.  I've adjusted your template automatically to change it to /config

 

Personally, I'd like the paths mentioned above to be filled out in the template.  That way it's closer to a 1 click install.  Only if the user has changed the default appdata path (a rarity) would they need to adjust vs right now everyone has to change the paths

[ZappyZap]

5 minutes ago, Squid said:

Personally, I'd like the paths mentioned above to be filled out in the template.  That way it's closer to a 1 click install.  Only if the user has changed the default appdata path (a rarity) would they need to adjust vs right now everyone has to change the paths

Got it 
thanks @Bleak to start the discussion, i will update the template 

[Bleak]

23 hours ago, ZappyZap said:

Got it 
thanks @Bleak to start the discussion, i will update the template 

Thanks and again thank you for keeping this alive!

[ZappyZap]

Template has been updated.
Thanks

[milfer322]

Hello,

The docker its work fine but I need increase the shm partition, but I cant.

 

I tried the first fix from this website, https://aricodes.net/posts/pihole-ftl-restarting/ add the variable shm_size with the space 1g and dont work.

 

How can increase the partition with this docker?

 

Thanks so much!!

[ZappyZap]

1 hour ago, milfer322 said:

Hello,

The docker its work fine but I need increase the shm partition, but I cant.

 

I tried the first fix from this website, https://aricodes.net/posts/pihole-ftl-restarting/ add the variable shm_size with the space 1g and dont work.

 

How can increase the partition with this docker?

 

Thanks so much!!

I will have a look at this site 
but try add 

--mount type=tmpfs,destination=/run

in extra parameters and let me know 

 

also can you describe what you are trying to fix , and wat issue you facing ?

Edited January 19, 2023 by ZappyZap

[lgnmcrules]

Hello, I am having the problem that after updating to the most recent version yesterday, it no longer works.  The error I get in the docker is this: 

And I notice that it must be a permission issue, right?  So I go change the files from "root" ownership back to "nobody".  However, after doing this, it immediately returns back to being owned by "root" after it is turned back on.  (Same thing for the "UNKNOWN owner.)

Looking at the logs in pihole when it is started up shows this:

And these files that it is referencing are files that keep getting reset to "root" ownership for a reason I don't know how to fix.

 

How do I resolve this issue?  

[ZappyZap]

what version are you runing ?
in the last 48 hours , pihole push 3 versions

[lgnmcrules]

2 minutes ago, ZappyZap said:

what version are you runing ?
in the last 48 hours , pihole push 3 versions

I am running v5.15

[ZappyZap]

can you do a 
ls -la /etc/pihole/

ls -la /etc/pihole/

inside the container 
please

 

[lgnmcrules]

9 minutes ago, ZappyZap said:

can you do a 
ls -la /etc/pihole/

ls -la /etc/pihole/

inside the container 
please

 

[ZappyZap]

did you mess with chmod and chown ?
your perm seem off ...
 

i will have to check thise a bit more closely....

[lgnmcrules]

6 minutes ago, ZappyZap said:

did you mess with chmod and chown ?
your perm seem off ...
 

i will have to check thise a bit more closely....

When the issue started, I tried setting the perms of the files it couldn't access to "nobody", but pihole kept setting them back to "root" or "UNKNOWN"

[ZappyZap]

try

chown pihole:pihole /etc/pihole/gravity.db*

and let me know 

[lgnmcrules]

12 minutes ago, ZappyZap said:

try

chown pihole:pihole /etc/pihole/gravity.db*

and let me know 

It didn't do much of anything except set the owner to UNKNOWN on the gravity.db* files

[ZappyZap]

unknown on the host (unraid) right....
OK
restart the container  

[lgnmcrules]

3 minutes ago, ZappyZap said:

unknown on the host (unraid) right....
OK
restart the container  

After restarting it is still like this:

And the directory has changed back to this:

 

[ZappyZap]

i would like you redeploy the container , from scratch , and see if it work.

stop the container
rename /user/appdata/pihole to  /user/appdata/pihole.bkp

and redeploy the container form scratch

let see if that work.....

 

i have the feeling this have nothing to do with the container but something else

let me know

Edited January 20, 2023 by ZappyZap