> It is not chrooted but running in an unprivileged LXC container, though
> that should not make a difference for Unbound writing its log inside the
> container, or should it perhaps?
Have tried the below variations and each is met with the same outcome ->
error: Could not open logfile
> Is unbound chrooted? If so, that would probably prevent it to access
> to the /var/log directory. Look for the 'chroot' configuration option
> in your unbound.conf file.
It is not chrooted but running in an unprivileged LXC container, though
that should not make a difference for Unbound
Hi,
> Archlinux current amd64
> Unbound 1.71
>
> Try as I might Unbound is not writing to logfile: "/var/log/unbound.log"
> and use-syslog: no.
>
> Would appreciate if someone could let me know.
Is unbound chrooted? If so, that would probably prevent it to access
to the /var/log directory.
