Jump to content
spants

[SUPPORT] pihole for unRaid - Spants repo

635 posts in this topic Last Reply

Recommended Posts

On 12/10/2018 at 1:48 PM, pcss said:

How do I update this docker? I installed using the YouTube video originally referred to. 4.1 is out and it's notifying me of updates. In the docker settings the repo is set to pihole/pihole:latest and I've changed the Docker URL from the diginc to https://hub.docker.com/r/pihole/pihole/

Thanks!

I wonder the same thing, mine is set to pihole/pihole:latest but no updates to 4.1 as of yet :S

Share this post


Link to post
36 minutes ago, ruvil said:

I wonder the same thing, mine is set to pihole/pihole:latest but no updates to 4.1 as of yet :S

 

You can check the Docker release versions here: https://hub.docker.com/r/pihole/pihole/tags/

 

The latest official "release" was delivered 2 months ago. You can try the dev_amd64 or dev releases if you wish.

Share this post


Link to post

What's the correct 

 

Repository:

 

&

 

Docker Hub URL:

 

 

 

Looks like it got renamed from diginc/pi-hole to pihole/pihole

 

So should it be:

 

pihole/pihole:latest

 

&

 

https://hub.docker.com/r/pi-hole/pi-hole

 

Share this post


Link to post
1 hour ago, CowboyRedBeard said:

What's the correct 

 


Repository:

 

&

 


Docker Hub URL:

 

 

 

Looks like it got renamed from diginc/pi-hole to pihole/pihole

 

So should it be:

 


pihole/pihole:latest

 

&

 


https://hub.docker.com/r/pi-hole/pi-hole

 

 

yes - you should change to this new repository. Unfortunately when I updated the template, this does not roll down to existing users

Share this post


Link to post

I changed it to that what u said but i get:

Dec 13 00:01:46 Unraid-Server nginx: 2018/12/13 00:01:46 [error] 5215#5215: *1960729 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.86.42, server: , request: "POST /Dashboard/UpdateContainer?xmlTemplate=edit:/boot/config/plugins/dockerMan/templates-user/my-pihole.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.86.2:81", referrer: "http://192.168.86.2:81/Dashboard/UpdateContainer?xmlTemplate=edit:/boot/config/plugins/dockerMan/templates-user/my-pihole.xml"

 

and my image is no abandomed... wtf

Share this post


Link to post

Hello,

I had running pihole latest docker without problems for 14 days.

Now DNS services are running :

docker exec pihole pihole status
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

But, dnsmasq, lighttpd and pihole-FTL are not running:

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is
[✗] lighttpd daemon is
[✗] pihole-FTL daemon is

If I start manually lighttpd, it dies 30 - 60 sec after.

I tried deleting and rebuilding container from scratch, but it's not working.

I also tried dev_amd64. Behavior was same, unfortunately.

 

Anyone with ideas?

 

Thanks

 

Share this post


Link to post

Is it possible to install things like DNScrypt and Unbound with the docker version or do we need the "normal" installations for that (thus VM or raspberry pi)?

Share this post


Link to post

So to give some feedback if u change to the official pihole container, you need to remove your old pihole and start from scratch, that worked for me. much faster now, it seems.

 

But u need to do all settings manually via docker arguments and such things... anooying^^

Edited by nuhll

Share this post


Link to post
1 minute ago, nuhll said:

So to give some feedback if u change to the official pihole container, you need to remove your old pihole and start from scratch, that worked for me. much faster now, it seems.

 

But u need to do all settings manually via docker arguments and such things... anooying^^

Ok, useful feedback but that wasn't my experience. I changed the repository line and applied.

Share this post


Link to post
5 minutes ago, spants said:

Ok, useful feedback but that wasn't my experience. I changed the repository line and applied.

I dont know. I just did that, but unraid become unresponsible, after it came back, the docker was "abandomed image" without any way to edit it anymore...

 

anyway that much config opotions doesnt exist... ;) so its not that much work.

Edited by nuhll

Share this post


Link to post
 
yes - you should change to this new repository. Unfortunately when I updated the template, this does not roll down to existing users
You want me to have FCP issue a comment asking users to change the repository?

Sent via telekinesis

Share this post


Link to post
On 12/13/2018 at 2:20 PM, Squid said:

You want me to have FCP issue a comment asking users to change the repository?

Sent via telekinesis
 

... Or I could just rename the template as V2 and mark the original as depreciated? What works best do you think?

Share this post


Link to post

I like the deprecated and a re-release of the template.  Since it's a new repository, effectively it is a different app

Share this post


Link to post
On 12/20/2018 at 2:23 AM, CowboyRedBeard said:

It would be awesome to add this... or at least maybe someone could create a docker of CloudFlareD :

 

https://visibilityspots.org/dockerized-cloudflared-pi-hole.html

In the post he is using a containerized version of cloudflared. I personally use https://hub.docker.com/r/rix1337/docker-dnscrypt/ and point pihole to it as the upstream DNS.

Share this post


Link to post
5 hours ago, CowboyRedBeard said:

Does it just take a few days for the docker image to catch up for updates? When I go to the admin page it shows there is an update available, but when I "check for updates" in the docker tab of unraid it doesn't show an available update for the docker????

 

I do have: 

pihole/pihole:latest

https://hub.docker.com/r/pihole/pihole/

Yes, you need to look at the tags tab on the docker hub page. You can see that latest hasn't been updated for 9 days right now. The updates you're seeing on the admin page are PiHole updates. You can update them in the container, but they will only live as long as the container is around. It looks like they've started dev containers of the latest updates, so probably testing it now.

Share this post


Link to post

I've been running pihole on this docker for a few months. It works really well. Thanks for all your work on this. I am, however, running into a problem with the logs. The logs are going into /var/log/pihole inside the docker image. I can't see any way to change that; nor can I see any way to truncate the logs.I've read the first post, but don't see how I can do this as most of these instructions no longer seem to apply.

 

So, how can I clear my pihole logs on a schedule?

 

Again, thanks for all your work on this. It truly is a great tool!

Share this post


Link to post
On 12/26/2018 at 1:45 PM, Big Dave Diode said:

I've been running pihole on this docker for a few months. It works really well. Thanks for all your work on this. I am, however, running into a problem with the logs. The logs are going into /var/log/pihole inside the docker image. I can't see any way to change that; nor can I see any way to truncate the logs.I've read the first post, but don't see how I can do this as most of these instructions no longer seem to apply.

 

So, how can I clear my pihole logs on a schedule?

 

Again, thanks for all your work on this. It truly is a great tool!

I've never tried to change the log storage length so I'm not an expert.  I think you can edit the "pihole-FTL.conf" file in the appdata folder to set when things get flushed.  See link below.  You should look at the "MAXLOGAGE" setting and / or the "MAXDBDAYS" from the looks of things.

https://discourse.pi-hole.net/t/how-to-set-a-limit-to-log-file-length-to-maximum-used-log-file-space/6482

My understanding is that the logs are short term storage (default 24 hours stored in the image) and the database is long term storage (default 365 days stored in the appdata folder outside the image).

 

As for if you are concerned about the logs being stored inside the container image, you could maybe do the following to move the log storage out of the image.

image.png.d8078adee7dee471bf2d40099bf5ecf5.png

Edited by FDM80

Share this post


Link to post
10 hours ago, L0rdRaiden said:

How can I override the resolution of a domain to a local host using this docker?

If I try to do this

https://serverfault.com/questions/796305/is-it-possible-to-override-a-single-domain-name-using-dnsmasq

Pihole docker fails, and after reboot the configuration is reset.

Is there a way to add this config without breaking anything and permanently?

 

It look likes this would require some modifications in the template or docker, I'm not sure, see this.

https://github.com/pi-hole/docker-pi-hole/issues/260

Would be possible to implement it in this docker? @spants

Share this post


Link to post
19 hours ago, L0rdRaiden said:

 

It look likes this would require some modifications in the template or docker, I'm not sure, see this.

https://github.com/pi-hole/docker-pi-hole/issues/260

Would be possible to implement it in this docker? @spants

can you try this:

In the appdata directory/dsnmasq.d/02-custom-LAN.conf file, it refers to adding hosts to appdata directory/pihole/custom-LAN.list file.

 

You will need to create it if not there..... Let me know...

Share this post


Link to post
4 hours ago, spants said:

can you try this:

In the appdata directory/dsnmasq.d/02-custom-LAN.conf file, it refers to adding hosts to appdata directory/pihole/custom-LAN.list file.

 

You will need to create it if not there..... Let me know...

Thanks, it worked

 

imagen.png.57827cb7ea12e9d71b6da061b493c012.png

And then as you said creating custom-LAN.list in the pihole folder

Share this post


Link to post

I'm having trouble getting this container to pick up an IPv6 address. I have IPv6 configured in both the main network settings and the docker settings. I have the container setup to use br0 and use a fixed IPv4 address. However, when I open a console in the container and run 'ip -6 addr' it shows nothing. I'm on Unraid v6.6.6 with the default IPv6 settings.

 

Does using a static IPv4 address cause issues with IPv6?

Share this post


Link to post

I've been using pihole running on a raspberry pi for a few months and no problems. I migrated over to this docker but have a problem. My sonarr docker is no longer unable to resolve dns lookups. The sonarr docker is running on 192.168.1.2 (same as the unraid server) and pihole is on 192.168.1.10 (same ip I was using when running on raspberry pi). No other docker is using port 53 or 67. If I shutdown the pihole docker and restart the raspberry pi, sonarr starts resolving dns again.

 

I feel like I'm missing something basic... Ideas?

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.