When using the FTLCONF_LOCAL_IPV4 enviroment variable in the composer file it will not overwrite the FTLCONF_LOCAL_IPV4 set during the docker build of the source image for the pihole docker aka in the Dockerfile.
Only way i have found to overwrite this enviroment variable so far was to use the image as a base and define FTLCONF_LOCAL_IPV4 again with the desired IP instead of beeing able to set this up in the composer file
Related Issues
[x] I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar
How to reproduce the issue
Environment data
Operating System: Rasbian
Hardware: RasPi 4B
Kernel Architecture:
Docker Install Info and version:
Software source: official docker-ce
Supplimentary Software:
Hardware architecture:
docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
any additional info to help reproduce
These common fixes didn't work for my issue
[x] I have tried removing/destroying my container, and re-creating a new container
[ ] I have tried fresh volume data by backing up and moving/removing the old volume data
[ ] I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
[ ] I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
[ ] I have tried running without my volume data mounts to eliminate volumes as the cause
If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.
This is a: Bug
Details
When using the FTLCONF_LOCAL_IPV4 enviroment variable in the composer file it will not overwrite the FTLCONF_LOCAL_IPV4 set during the docker build of the source image for the pihole docker aka in the Dockerfile. Only way i have found to overwrite this enviroment variable so far was to use the image as a base and define FTLCONF_LOCAL_IPV4 again with the desired IP instead of beeing able to set this up in the composer file
Related Issues
How to reproduce the issue
Environment data
docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
any additional info to help reproduce
These common fixes didn't work for my issue
docker run
example(s) in the readme (removing any customizations I added)If the above debugging / fixes revealed any new information note it here. Add any other debugging steps you've taken or theories on root cause that may help.