Closed jhomen368 closed 6 months ago
You can create a directory with the name opt-unbound-etc-unbound
& move everything from ${PWD}/opt/unbound/etc/unbound
, just like you did with etc-pihole
. And then use -v "${PWD}/opt-unbound-etc-unbound:/opt/unbound/etc/unbound"
I was hoping that it would prepopulate default configurations. I just looked at the upstream unbound and it does the same thing so think this is the current expected behavior.
Pre-populating is a bit more difficult with my particular use case since I'm using a Kubernetes cluster with longhorn which does dynamic volume assignment. I'm just guessing but I probably have to spin pihole-unbound pod up, let it fail, down that pod leave leave the volume behind. Finally, mount that volume to another pod (unrelated to pihole) make the changes there detach that volume and then re-spin up the pihole-unbound pod. I'll figure something out thanks though!
@jhomen368 I've misread the logs first. It correctly found the unbound.conf
but seems the a-records.conf
and srv-records.conf
files are missing in your custom directory. Copy the missing files a-records.conf
and srv-records.conf
into the same directory as the unbound.conf file inside the container. Your issue will be fixed.
I put in a feature request for the upstream unbound container https://github.com/MatthewVance/unbound-docker/issues/171.
I'm working on it, soon image will be updated.
Thanks! I really appreciate it
Pushed hot fix updated image!
This is a: Run Issue
Details with Docker log
Related Issues
N/A
How to reproduce the issue
Environment data
Troubleshooting Logs
Works:
Doesn't Work:
Leaves container in a reboot loop
Upload the unbound log file
unbound.log is a 0 byte file with no content
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.
Files seem to exist:
I also noticed this when I was trying to deploy the container into a Kubernetes cluster, at first I thought it was an issue with my manifests but when I tried it locally it gave me the same behavior. Once I defined the volume for unbound per the readme it starting rebooting and wouldn't come up. Am I missing something?