simono41/docker-pihole-unbound
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Compare commits

base: simono41:2022.09.3
Branches Tags
simono41:main
simono41:2023.11.0
simono41:2023.05.2
simono41:2023.02.2
simono41:2023.01.10
simono41:2022.12
simono41:2022.11.2
simono41:2022.11.1
simono41:2022.10
simono41:2022.09.3
simono41:2022.08.2
simono41:2022.07.1
simono41:2022.07
simono41:2022.05
simono41:2022.04.3
simono41:2022.04.2
simono41:2022.02.1-2
simono41:2022.02.1
simono41:2022.01.1
simono41:2021.12.1
simono41:2021.10.1
simono41:2021.10
simono41:2021.09
simono41:v5.8.1-1
simono41:v5.8.1
simono41:v5.8
simono41:v5.7-bridge
simono41:v5.7
simono41:v5.6
simono41:v5.5.1
simono41:1.0.0
...
compare: simono41:main
Branches Tags
simono41:main
simono41:2023.11.0
simono41:2023.05.2
simono41:2023.02.2
simono41:2023.01.10
simono41:2022.12
simono41:2022.11.2
simono41:2022.11.1
simono41:2022.10
simono41:2022.09.3
simono41:2022.08.2
simono41:2022.07.1
simono41:2022.07
simono41:2022.05
simono41:2022.04.3
simono41:2022.04.2
simono41:2022.02.1-2
simono41:2022.02.1
simono41:2022.01.1
simono41:2021.12.1
simono41:2021.10.1
simono41:2021.10
simono41:2021.09
simono41:v5.8.1-1
simono41:v5.8.1
simono41:v5.8
simono41:v5.7-bridge
simono41:v5.7
simono41:v5.6
simono41:v5.5.1
simono41:1.0.0

7 commits
2022.09.3 ... main

Author SHA1 Message Date
Chris Crowe
33cebb3cfe
Upgrading base container to 2023.05.2 (#213) 2023-07-02 11:56:44 -07:00
Chris Crowe
55c88afaf8
Updating base container to 2023.02.2 (#202) 2023-03-22 08:26:30 -07:00
Chris Crowe
96038ebbfa
Upgrading base container to 2022.12 (#190) 2022-12-29 19:04:19 -08:00
Chris Crowe
226fddf83a
Upgrading base container to 2022.11.2 (#186) 2022-12-16 14:25:22 -08:00
Chris Crowe
025a0a20c3
Upgrading base container to 2022.11.1 (#181) 2022-11-24 11:50:15 -08:00
Mats Oftedal
e936dbb95c
Updated pihole container version to 2022.10 (#173) 
Updated pihole container version to 2022.10
 2022-10-12 22:04:55 -07:00
Xabi
d60ebfcd7d
Disable so-rcvbuf custom value (#166) 
* Disable so-rcvbuf custom value

Using the default value is most of the time enough for a normal operation.

This removes an Unbound warning that complains about not having the requested 1m or more for kernel buffering.

* Corrected indentation

* Include additional information

Explained how to correctly enable so-rcvbuf.

Co-authored-by: burnbabyburn <xyz258@abwesend.de>

Co-authored-by: burnbabyburn <xyz258@abwesend.de>
 2022-10-12 22:02:36 -07:00
2 changed files with 3 additions and 2 deletions
Show stats Expand all files Collapse all files

2
one-container/pihole-unbound/VERSION
View file

@ -1 +1 @@
2022.09.3 2023.05.2

3
one-container/pihole-unbound/unbound-pihole.conf
View file

@ -44,7 +44,8 @@ server:
num-threads: 1 num-threads: 1
# Ensure kernel buffer is large enough to not lose messages in traffic spikes # Ensure kernel buffer is large enough to not lose messages in traffic spikes
so-rcvbuf: 1m # Be aware that if enabled (requires CAP_NET_ADMIN or privileged), the kernel buffer must have the defined amount of memory, if not, a warning will be raised.
#so-rcvbuf: 1m
# Ensure privacy of local IP ranges # Ensure privacy of local IP ranges
private-address: 192.168.0.0/16 private-address: 192.168.0.0/16