> 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 /var/log/unbound.log: No such file or directory 1. no file unbound.log in /var/log and thus expecting unbound to create it 2. created file unbound.log in /var/log manually with mask 0755 3. set logfile: "/var/log/unbound.log" 4. set logfile: /var/log/unbound.log
