You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Container fails to start up due to Unbound DNSSEC validator module failing. Unbound claims that it can't access var/root.key. I haven't been using DNSSEC on the clients anyway (yet), however, I have been using this exact same Unbound config with the exact same Unbound image on a different server, and had no such issues.
Moreover, the Docker volume is mounted as read-write and there is initially no var/ at all. The the unbound.sh script does the right thing in this situation:
A workaround is to turn off DNSSEC by deleting the auto-trust-anchor-file directive, after which Unbound loads without any problems. But I'd prefer to eventually get back to a DNSSEC-validated setup, at which point I expect that this will reappear.
Any ideas?
Error messages
unbound | [1720637715] unbound[1:0] notice: init module 1: validator
unbound | [1720637715] unbound[1:0] error: unable to open var/root.key for reading: Permission denied
unbound | [1720637715] unbound[1:0] error: error reading auto-trust-anchor-file: var/root.key
unbound | [1720637715] unbound[1:0] error: validator: error in trustanchors config
unbound | [1720637715] unbound[1:0] error: validator: could not apply configuration settings.
unbound | [1720637715] unbound[1:0] error: module init for module validator failed
unbound | [1720637715] unbound[1:0] fatal error: failed to setup modules
Description
Container fails to start up due to Unbound DNSSEC validator module failing. Unbound claims that it can't access
var/root.key
. I haven't been using DNSSEC on the clients anyway (yet), however, I have been using this exact same Unbound config with the exact same Unbound image on a different server, and had no such issues.Moreover, the Docker volume is mounted as read-write and there is initially no
var/
at all. The the unbound.sh script does the right thing in this situation:A workaround is to turn off DNSSEC by deleting the
auto-trust-anchor-file
directive, after which Unbound loads without any problems. But I'd prefer to eventually get back to a DNSSEC-validated setup, at which point I expect that this will reappear.Any ideas?
Error messages
To Reproduce
9bd7e8b4e75d
)local-zone.conf
andforward-records.conf
files contain justforward-zone
,forward-addr
,local-zone
,local-data
andlocal-data-ptr
.The text was updated successfully, but these errors were encountered: