Closed Frostymnl closed 1 year ago
It shouldn't because I specifically use --config
parameter here to force the new location -> https://github.com/jacklul/pihole-updatelists/blob/master/install.sh#L184 and if it didn't work it would error out
Doesn't seem to happen in my virtual machine, although the instance doesn't start properly ([✗] DNS resolution is not available
bug?) I can see from the log file that it used the config in the mounted volume.
Yeah, I located the log file too, and it said that it is using the config from the mounted volume, but if my memory is correct it was not reflecting that on the UI. When I have a second I will try spinning this up again from scratch.
When using the sample docker-compose it seems the custom configuration you set up in ./etc-pihole-updatelists/pihole-updatelists.conf are not being utilized.
Steps to reproduce:
; Remote list URL containing list of adlists to import ; URLs to single adlists are not supported here! ADLISTS_URL="https://v.firebog.net/hosts/lists.php?type=tick"
; Remote list URL containing exact domains to whitelist WHITELIST_URL="https://raw.githubusercontent.com/anudeepND/whitelist/master/domains/whitelist.txt"
; Remote list URL containing regex rules for whitelisting REGEX_WHITELIST_URL=""
; Remote list URL containing exact domains to blacklist ; This is specifically for handcrafted lists only, do not use regular blocklists here! BLACKLIST_URL=""
; Remote list URL containing regex rules for blacklisting REGEX_BLACKLIST_URL="https://raw.githubusercontent.com/mmotti/pihole-regex/master/regex.list"