Jump to content

[SUPPORT] pihole for unRaid - Spants repo


Recommended Posts

  • 4 weeks later...
Posted

I am having this weird issue where if i start the pihole docker, it changes the ip address of my entire server which messes with the already established dhcp reservation that i had set for it before hand. I thought that the pihole would count as its own device but in my router settings it does not appear as such. a little help would be appreciated.

  • Like 1
  • 1 month later...
  • 2 months later...
Posted (edited)

My pihole docker is getting quite large - the container is 9.2 GB and the Writable column is 8.89GB.  How do I troubleshoot this and see what the cause is?  The pihole-FTL.db file is about 3.4GB but that appears to be in appdata.

 

What could be causing this?

 

edit - I updated the pihole docker and that fixed the problem.  The size fell by over 95% to 328MB.  Leaving this comment here in case it helps someone in the future.

Edited by wayner
  • 4 weeks later...
Posted
On 5/14/2024 at 11:28 PM, wayner said:

My pihole docker is getting quite large - the container is 9.2 GB and the Writable column is 8.89GB.  How do I troubleshoot this and see what the cause is?  The pihole-FTL.db file is about 3.4GB but that appears to be in appdata.

 

What could be causing this?

 

edit - I updated the pihole docker and that fixed the problem.  The size fell by over 95% to 328MB.  Leaving this comment here in case it helps someone in the future.

Thanks for this! Force update the container shrunk the container size from 5GB to 300MB.  It must be a log file or something that should be mapped to the appdata dir instead of inside the container.  

Posted (edited)

I have an older unRAID server that was also getting the docker partition full problem.  I found a way to fix it on these forums - edit your docker and go into extra parameters.  Put this in --log-opt max-size=50m --log-opt max-file=1 as extra parameters and that is supposed to limit your logs to 50 MB each.

 

edit - Make sure that you have advanced mode turned on to see the extra parameters button.

Edited by wayner
  • 3 months later...
Posted (edited)

All 4 of these issues are the same, and I am having this issue also. Can anyone help at all? I have seem many on Reddit also.

 

  

On 3/18/2023 at 6:29 PM, onesterkin said:

Help needed. I've installed Pi-hole as container using Spaceinvader's guide and it seems not to be working.

Unraid server itself is configured to use Cloudflare/Google DNS (so not relying on pi-hole)

Pi-Hole docker configured to use custom/br0 network with dedicated fixed ip address 192.168.2.201, the same for Server IP variable. 

Docker settings - Host access available is set to yes, using macvlan (the latter doesn't make much difference compared to ipvlan actually).

I can access Pi-hole WebUI, but as soon as I login into shell, I cannot ping anything out of host network (e.g. router, dns servers themselved are unavailable).

Thus DNS resolving is not available, etc.

Suppose I miss something simple here, but cannot find what.


 

  

On 11/22/2023 at 9:21 AM, independence said:

Hi all,

 

when I´m trying to add a new adlist, there is an error:

"While executing: attempt to write a readonly database"

 

Do you already know what went wrong?

 

Thanks



 

  

On 12/12/2023 at 1:28 PM, orlando500 said:

Hi i have had pihole working for a long time, but i did do an update and it broke somehow.

I got the error "DNS resolution is not available" in the log and the blocking list stats is showing -2 in the dashboard.

 

The client resolution using pihole still works... any pointers? cant seem to find a solution that works

 

Edited by chrisp7
  • 1 month later...
Posted
On 6/11/2024 at 4:23 PM, wayner said:

I have an older unRAID server that was also getting the docker partition full problem.  I found a way to fix it on these forums - edit your docker and go into extra parameters.  Put this in --log-opt max-size=50m --log-opt max-file=1 as extra parameters and that is supposed to limit your logs to 50 MB each.

 

edit - Make sure that you have advanced mode turned on to see the extra parameters button.

I had that setting, yet my piHole had grown to 22+GB's. 

I removed it entirely and fixed the issue. 

 

I did, as I mentioned, have that log max-size setting enabled.. I have it for all my docker containers actually since Plex misbehaved one time. 

Anyone actually investigate the root cause? I have been noticing that piHole has essentially been blocking nothing in the WebUI. Updated configuration instructions or something, maybe? 

  • 1 month later...
Posted

I agree in that the log max size is not working.  My log size got up to 4.6GB.  It seems like logs are being written to somewhere in the docker rather than the appdata folder.  This sure seems to be a bug to me.

Posted
2 hours ago, wayner said:

I agree in that the log max size is not working.  My log size got up to 4.6GB.  It seems like logs are being written to somewhere in the docker rather than the appdata folder.  This sure seems to be a bug to me.

Hi all

 

I created this template many years ago as a wrapper for the offical pihole docker and I am not surpised that a number of items may not work correctly. I changed my setup to use opnsense/adguard hence I have not seen the problems myself as I dont use it.

Regarding the logs, try creating a log directory in the pihole appdata directory and add the following path:

(run the docker for a while and see if the logs are written to the host instead of the container)

 

image.png.377be3daa5a7c92c82483c89d191f2f3.png

Posted

Thanks - I just did that and I see that the docker created a pihole folder off of my /appdata/pihole/log folder, as in /appdata/pihole/log/pihole,  and it has created two files so far - pihole.log and FTL.log.

 

So it seems to have worked. I will keep an eye on the docker size.

 

Thanks!

Posted

FYI, there seems to be another similar issue.  The pihole-FTL.db file also gets very large.  Currently this file is in /appdata/pihole/pihole on my server.

 

Apparently you can limit the amount of logging that goes to this database in the pihole-FTL.conf file.  I have to figure out how to do this.

Posted (edited)

@spants I believe one other action is needed - you need to create a lighttpd folder under the logs folder in appdata.

 

I noticed that pihole wasn't running so I checked the logs which showed the text below.  I manually created a /appdata/pihole/log/lighttpd folder and now it seems to work ok.  When the docker restarted it created files in that lighttpd folder.

 

install: cannot create regular file '/var/log/lighttpd/access-pihole.log': No such file or directory
install: cannot create regular file '/var/log/lighttpd/error-pihole.log': No such file or directory
chown: cannot access '/var/log/lighttpd': No such file or directory
chmod: cannot access '/var/log/lighttpd/access-pihole.log': No such file or directory
chmod: cannot access '/var/log/lighttpd/error-pihole.log': No such file or directory
2024-12-30 17:17:53: configfile.c.1290) opening errorlog '/var/log/lighttpd/error-pihole.log' failed: No such file or directory
2024-12-30 17:17:53: server.c.1509) Opening errorlog failed. Going down.
Stopping lighttpd
lighttpd: no process found

 

Edited by wayner
fix typo
  • Like 1
Posted

well spotted - I dont run any install scripts in the template as it just uses the official docker image. With unraid, you may have to do these tweaks!....

 

Posted

I want to use pihole as a dns server together with npm in order to use local domain. I want to redirect 192.168.178.45:5055 to jellyseerr.local. To do so i followed this tutorial.

 

I created a new host in npm which use jellyseerr.local and points it to 192.168.178.45:5055. NPM itself is reachable under 192.168.178.2. After that i created a dns record in pihole which is jellyseerr.local -> 192.168.178.2. So i would guess, if a user tries to access jellyseerr.local, the network will look into npm because 192.168.178.2 and npm redirects to 192.168.178.45:5055. In reality nothing happens, jellyseerr.local is not reachable. I also added the ip of pihole (which is 192.168.178.45 as it runs on my unraid) in my FritzBox under network > network settings > ip v4 > local dns server.

 

What did i miss?

Screenshot 2025-01-02 173920.png

Screenshot 2025-01-02 173930.png

Screenshot 2025-01-02 174233.png

  • 2 weeks later...
Posted

Unraid 7, pihole, tailscale

 

Hello all,

 

I tried to activate the new Tailscale support for my pihole container. Upon applying and restarting the container, it seems to be running but I cannot display the logfile or the console of the container. A window briefly pops up but closes immediately. Upon deactivating the tailscale feature in the container configuration, all is well again.

 

Has anyone had success with this so far?

 

Many thanks.

Posted (edited)
6 hours ago, AlainF said:

Unraid 7, pihole, tailscale

 

Hello all,

 

I tried to activate the new Tailscale support for my pihole container. Upon applying and restarting the container, it seems to be running but I cannot display the logfile or the console of the container. A window briefly pops up but closes immediately. Upon deactivating the tailscale feature in the container configuration, all is well again.

 

Has anyone had success with this so far?

 

Many thanks.

Same issue.

 

Tried with custom:br0 network, fixed serverIp. But it apparently can't download some of the tailscale packages needed...

 

 

  Temporary failure resolving 'deb.debian.org'
Err:3 http://deb.debian.org/debian bullseye-updates InRelease
  Temporary failure resolving 'deb.debian.org'
Reading package lists...
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian-security/dists/bullseye-security/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease  Temporary failure resolving 'deb.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package wget
ERROR: Unraid Docker Hook script throw an error!
       Starting container without Tailscale!

 

ok got it working by specifying dns for the container: --dns=8.8.8.8

Edited by nabbl

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.

×
×
  • Create New...