posts/pihole-containerized/

[giscus[bot]]

posts/pihole-containerized/

We know you’ve heard of Pihole and we know you are probably aware of how to install it but… have you tried running it on Docker and Kubernetes using Rancher? Have you configured it for pfSense? Don’t worry, I figured out all the hard stuff for you. So let’s consolidate some hardware and services.

https://technotim.live/posts/pihole-containerized/

[OneBiteAidan]

For anyone who was struggling w/ receiving 403 forbidden errors after punching in the local IP of the docker container. You need to add a /admin to the end of the URL you put into your browser. i.e /admin

[baz-snow-ss]

Is this still valid ?, I tired to install resolvconf and I get

portainer@portainer:~$ sudo apt-get install resolvconf
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'systemd-resolved' instead of 'resolvconf'
systemd-resolved is already the newest version (253.5-1ubuntu6.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
portainer@portainer:~$ sudo systemctl enable resolvconf.service
Failed to enable unit: Unit file resolvconf.service does not exist.
portainer@portainer:~$ sudo nano /etc/resolvconf/resolv.conf.d/head
portainer@portainer:~$

and the head file does not exist.
https://manpages.debian.org/buster/systemd/resolvectl.1.en.html#COMPATIBILITY_WITH_RESOLVCONF(8)
cat /etc/resolv.conf

portainer@portainer:~$ cat /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search .
portainer@portainer:~$