.. SPDX-License-Identifier: GPL-3.0-or-later
+
+.. include:: deployment-warning.rst
+
.. _advanced-no-manager:
*************************
*************************
-.. warning::
-
- This page is intended for experienced users only. If you follow these instructions, you are not protected from footguns elimited with the introduction of the manager. However, if you want to continue using Knot Resolver as before version ``6.0.0`` this is chapter for you.
-
- For new and less experienced users, we recommend using the newer approach starting in :ref:`Getting Started <gettingstarted-intro>` chapter.
-
-
There are a few downsides to using the Knot Resolver without the manager:.
* Configuration is a imperative Lua script and can't be properly validated without actually running it.
docker run --rm -ti -P docker.io/cznic/knot-resolver
-The configuration file is located at ``/etc/knot-resolver/config.yml`` and the cache is at ``/var/cache/knot-resolver``. Having persistent cache in a mounted volume will help a lot with performance just after restart.
+The configuration file is located at ``/etc/knot-resolver/config.yml`` and the cache is at ``/var/cache/knot-resolver``. We recommend configuring a persistent cache across container restarts.
.. warning::
The Knot Resolver can be started with the command ``knot-resolver``. You can provide an optional argument ``--config path/to/config.yml`` to load a different than default configuration file.
-The resolver does not have any external runtime dependencies and it should be able to run in most environments. The resolver does not interact with cgroups or namespaces and you can run it multiple times as long as you use a different runtime directory in the configuration.
\ No newline at end of file
+The resolver does not have any external runtime dependencies and it should be able to run in most environments. It should be possible to wrap it with any container technology.
+
+
+Multiple instances on a single server
+=====================================
+
+The only limitation for running multiple instances of Knot Resolver is that all instances must have a different runtime directory. There are however safeguards in place that should prevent accidental runtime directory conflicts.
+
+It is possible to share cache between multiple instances, just make sure that all instances have the same cache config and there is only a single garbage collector running (disable it in all but one config file).
\ No newline at end of file
.. SPDX-License-Identifier: GPL-3.0-or-later
+.. include:: deployment-warning.rst
+
Privileges and capabilities
===========================
.. SPDX-License-Identifier: GPL-3.0-or-later
+.. include:: deployment-warning.rst
+
Process management
==================
.. _usage-without-systemd:
+.. include:: deployment-warning.rst
+
*****************************************
Usage without systemd and without manager
*****************************************
--- /dev/null
+.. warning::
+
+ This page is intended for experienced users only. If you follow these
+ instructions, you are not protected from footguns elimited with the
+ introduction of the ``kres-manager``. However, if you want to continue
+ using Knot Resolver the same as before the version ``6.0.0`` this is a chapter
+ for you.
+
+ For new and less experienced users, we recommend using the newer approach
+ starting in the :ref:`Getting Started <gettingstarted-startup>` chapter.
\ No newline at end of file
:maxdepth: 1
deployment-systemd
- deployment-docker
deployment-manual
+ deployment-docker
deployment-advanced
.. toctree::