v6.0.11 confusion about default /management/unix-socket
Test point: Debian 12, defaults for this but some other stuff configured. Service fails to start:
knot_resolver.utils.modeling.exceptions.DataValidationError: Configuration validation error detected:
[/unix-socket] knot-resolver:knot-resolver has insufficient permissions to write/execute'/etc/knot-resolver'
Workaround: explicitly configure the path, e.g.:
management:
unix-socket: /run/knot-resolver/kres-api.sock
It's weird that it does start with empty (distro-installed) config, though
Edited by Vladimír Čunát