as mentioned in https://github.com/pi-hole/docker-pi-hole/issues/1323
It is worth noting that this page will exist on a bare metal fresh installation, too. Should we delete it? Probably not - we shouldn't touch that directory really - but in docker we have more control as we build the image from fresh each time. TL;DR, we can do things here that we shouldn't in bare metal installs Signed-off-by: Adam Warner <me@adamwarner.co.uk>
This commit is contained in:
parent
39d23d91e4
commit
4961bf4b1a
|
@ -92,6 +92,12 @@ sed -i $'s/)\s*reconfigurePiholeFunc/) unsupportedFunc/g' /usr/local/bin/pihole
|
|||
# (it is otherwise only updated when FTL is updated, which doesn't happen as part of the normal course of running this image)
|
||||
mv /etc/pihole/macvendor.db /macvendor.db
|
||||
|
||||
|
||||
## Remove the default lighttpd unconfigured config:
|
||||
rm /etc/lighttpd/conf-enabled/99-unconfigured.conf
|
||||
## Remove the default lighttpd placeholder page for good measure
|
||||
rm /var/www/html/index.lighttpd.html
|
||||
|
||||
if [ ! -f /.piholeFirstBoot ]; then
|
||||
touch /.piholeFirstBoot
|
||||
fi
|
||||
|
|
Loading…
Reference in New Issue