Open josh817 opened 1 year ago
Your root-hints file location is outside of the chroot.
Also see https://github.com/MatthewVance/unbound-docker/issues/28#issuecomment-541953720.
I have the same problem when I perform a complete restart. But I don't know what the root.hints has to do with the pid of unbound?
I'm running unbound behind a pihole so I don't use it as reverse Proxy.
ChatGPT mentioned that I should use Tini as entry point. But this is not in the container file.
Describe the bug Through my tinkering with unbound.conf settings to get it working, I am constantly stopping and duplicating my unbound container (I am using Portainer). It seems sporadic when it gives me the "warning unbound is already running as pid 1" in the log.
Expected behavior I typically "kill" the container when trying new conf files and then duplicate. I have now run into the problem where it doesn't matter if I Stop, Kill, Restart, Duplicate, or delete the container and build from scratch, even reboot the device entirely, I still get the PID 1 warning. I also delete the unbound.pid file in my directory and the problem persists. I've seen this in other peoples log files but never has it been addressed directly. I feel like it is a simple issue
Error messages warning unbound is already running as pid 1
EDIT: Here is my conf file. After some more poking around it looks like my problem root.hints. My only problem is that I do in fact have a root.hints in that directory that I update with this "wget https://www.internic.net/domain/named.root -qO- | sudo tee /srv/appdata/unbound/root.hints". While I am generally annoyed that root.hints won't work the way I'd like it to, I think Unbound defaults to the root.hints within /usr/share/dns, is that right?
server: ###########################################################################
BASIC SETTINGS
remote-control: control-enable: no