Inspired by #24 i set out to document the process of building the container locally while also documenting the automatic process with github actions

• Document local build process
• Document github actions build and publish process
• #28
• #27

For those that rely on the docker-compose.yaml file for installation/updating, the image number hasn't been updated to reflect the newly updated image.

Current:
image: aleksanderbl/pihole-unbound:2024.01.0

Update:
image: aleksanderbl/pihole-unbound:2024.02.0

2024.03.01 released: https://github.com/pi-hole/docker-pi-hole

To enable automatic container build and publish of containerversions in development i would like to have a github action that runs on all pushes to branches that are not main. Maybe add dev and date/time as a tag to ensure that it is not used for production.

• Add workflow file
• Add dev and date/time to tag
• Document what this action does according to #26

So this is probably more of an issue on my side, but any help would be greatly appreciated.

So atm i have a raspberry pi on IP 192.168.10.168 which is running the pihole and unbound. I also have my router running at 192.168.10.1. In my router i have configured 192.168.10.168 as my LAN DNS server

My compose look like this:

version: '3.5'

services:
  pihole:
    container_name: "pihole"
    image: aleksanderbl/pihole-unbound:2024.02.0
    hostname: "pihole"
    domainname: "pihole.local"
    ports:
      - "443:443/tcp"
      - "53:53/tcp"
      - "53:53/udp"
      - "81:80/tcp" #Allows use of different port to access pihole web interface when other docker containers use port 80
      - "5335:5335/tcp" # Uncomment to enable unbound access on local server
      # - 22/tcp # Uncomment to enable SSH
    environment:
      FTLCONF_LOCAL_IPV4: "192.168.10.168"
      TZ: "Europe/Stockholm"
      WEBPASSWORD: "my-secret-password"
      WEBTHEME: "default-dark"
      REV_SERVER: true
      REV_SERVER_TARGET: "192.168.10.1"
      REV_SERVER_DOMAIN: "local"
      REV_SERVER_CIDR: "192.168.0.0/16"
      PIHOLE_DNS_: "127.0.0.1#5335"
      DNSSEC: true
      DNSMASQ_LISTENING: single
      HOSTNAME: "pihole"
      DOMAIN_NAME: "pihole.local"
      VIRTUAL_HOST: "pihole.box"
    dns:
      - 127.0.0.1
    volumes:
      - "/home/sami/pihole/etc-pihole:/etc/pihole:rw"
      - "/home/sami/pihole/etc-dnsmasq:/etc/dnsmasq.d:rw"
    restart: unless-stopped

So the PIhole works and all, but for some reason my internet stops working unless i enable another DNS server in pihole. So now i have the setup above but i have also enabled Google (ECS, DNSSEC) for IPV4 now.

Any idea what it could be or how to debug this issue?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Current bundled version is 1.17.1 and the latest one is 1.20.0. Why?

CodeFactor found an issue: Do not use apt as it is meant to be a end-user tool, use apt-get or apt-cache instead

It's currently on:
pihole-unbound\Dockerfile:3

The security cases which refer to this are CVE-2023-50387 and CVE-2023-50868. Both vulnerabilities are remote exploitable and rated “high” severity. But Ubound 1.19.1 fixes these

The repo has become cluttered. I will by begin removing files that are not in use

Inspired by #24 I will add specific versions in the dockerfile and allow the renovate bot to ping me when a new release is available. While I am at it I will clean up the files for building the container and add documentation.

This gives the following tasks:

• Add specific version to dockerfile
• Ensure renovate recognizes the version in dockerfile
• #26

Hi there!

I'm fairly new to docker and have been messing around with the original repo of this container, and found yours which updates pihole and unbound. Thank you so much for these updates!

I have a few contributions that I'll make later on to this repo such as some documentation/variable additions due to Apple Privacy, etc.

A few questions:

1. Where are you setting the version for pihole in this? I see the older version in the VERSION file, but see a newer version in the pihole UI.

2. I'm able to successfully get your container working which is awesome, but how did you build and push this to docker hub? When I tried to create a custom version using the docker file and ran the build_and_push.sh I got the following error when trying to run the container:
   [i] pihole-FTL (no-daemon) will be started as pihole
   s6-rc: info: service _startup successfully started
   s6-rc: info: service pihole-FTL: starting
   s6-rc: info: service pihole-FTL successfully started
   s6-rc: info: service lighttpd: starting
   s6-rc: info: service lighttpd successfully started
   s6-rc: info: service _postFTL: starting
   s6-rc: info: service _postFTL successfully started
   s6-rc: info: service legacy-services: starting
   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
   services-up: info: copying legacy longrun unbound (no readiness notification)
   s6-rc: info: service legacy-services successfully started
   ifelse: fatal: unable to exec bash
   : No such file or directory

Perhaps I didn't build and push it to docker hub correctly, but I'm not sure how to push it properly.

Thanks again!!

Hi !, very good work!
For some reason the Dockerfile does not receive $PIHOLE_VERSION as an argument? You get it in the autobuild.yml. Regards. Adrian

And the unbound Debian bullseye-backport package hasn't been updated yet.

I will change the install method so that the image uses the bookworm-repo and then I will update this image when 1.19.1 is pushed to this tag. It seems to currently be in the unstable sid channel which I will not base the image on

Originally posted by @aleksanderbl29 in #40 (comment)

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option 'assignees' should be a list (Array)