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
Describe the bug
unbound does not work on the Linux development environment of a ChromeOS system, which is a debian container.
there are various ways this manifests itself
running unbound-anchor produces no output, exits with 0
running unbound-anchor -v produces the following:
/usr/share/dns/root.key has content
fail: the anchor is NOT ok and could not be fixed
now what?
as far as I can tell, this is about running on ChromeOS, same result using an alpine docker container.
Expected behavior
Two things are wrong here:
exit code 0 implies everything was fine but it failed silently
the error message is obscure and unhelpful
System:
Unbound version: 1.17.1
OS: Debian GNU/L:inux 12 (bookworm) on ChromeOS version 131
Describe the bug
unbound does not work on the Linux development environment of a ChromeOS system, which is a debian container.
there are various ways this manifests itself
unbound-anchor
produces no output, exits with 0unbound-anchor -v
produces the following:now what?
as far as I can tell, this is about running on ChromeOS, same result using an alpine docker container.
Expected behavior
Two things are wrong here:
System:
unbound -V
output:same problem running in an alpine:3.21.0 docker container that comes with
Additional information
Add any other information that you may have gathered about the issue here.
The text was updated successfully, but these errors were encountered: