Skip to content

Draft: knot-resolver6: the manager integration

Aleš Mrázek requested to merge amrazek/turris-os-packages:feature/knot-resolver6-manager into develop
  • Declarative configuration
    • config.yaml: static configuration
    • config.json: dynamic configuration, configuration created by the kresd.init script
  • Knot Resolver now starts with knot-resolver executable (the manager) and loads config.yaml and config.json configurations.

Knot Resolver should function smoothly on TurrisOS in the next release (6.0.16?) because minor adjustments were necessary (knot-resolver!1742, knot-resolver!1741).

To make everything perfect, it would need to add new knot-resolver user (replace kresd user) and rename kresd.init to knot-resolver.init. I didn't dare to do that (could break something else), but it's just a naming detail and it should work this way without problems.

I was unable to build the packages. I tried the dynamic configuration created in the init file, but it's possible that I may have overlooked or forgotten something.

TODO:

  • test package build
  • test dynamic configuration (config.json) created in init file
  • new knot-resolver user (optional)
  • rename kresd.init to knot-resolver.init (optional)

CC @vcunat

Merge request reports