[taler-docs] branch master updated: How to install Docker.

[gnunet]

This is an automated email from the git hooks/post-receive script.

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 772d3d0  How to install Docker.
772d3d0 is described below

commit 772d3d0f28250d2dbf57861a9d83e943bc8cdfad
Author: MS <ms@taler.net>
AuthorDate: Fri Nov 18 13:13:10 2022 +0100

    How to install Docker.
    
    And mention SystemD unit files related to test-worker
    and walletbuilder.
---
 taler-developer-manual.rst | 34 +++++++++++++++++++++++++---------
 1 file changed, 25 insertions(+), 9 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 3f41ee2..c488a8f 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -295,12 +295,21 @@ Demo Upgrade Procedure
 #. Navigate to the ``deployment.git/docker/demo`` directory.
 #. Refer to the README, or the smaller cheat sheet below.
 
-The deployment is based on rootless Docker, that is
-a SystemD unit in userspace: ``docker.service``.  The
-running daemon is reached by every Docker command at the
-address held into the ``DOCKER_HOST`` environment variable.
-Normally, it points to ``unix:///run/user/$(id -u)/docker.sock``.
-Such variable is automatically exported by ``~/.bashrc``.
+The deployment is based on rootless Docker, managed by the
+SystemD unit in userspace: ``docker.service``.  The running daemon
+is reached by every Docker command at the address held into the
+``DOCKER_HOST`` environment variable.  Normally, it points to
+``unix:///run/user/$(id -u)/docker.sock``.  Such variable is automatically
+exported by ``~/.bashrc``.
+
+.. note::
+
+   Should the rootless Docker be installed, run the following command
+   or consult the `official documentation 
<https://docs.docker.com/engine/security/rootless/>`_.
+
+  .. code-block:: console
+
+    $ curl -fsSL https://get.docker.com/rootless | sh
 
 Upgrading the ``demo`` environment should be done with care, and ideally be
 coordinated on the mailing list before.  It is our goal for ``demo`` to always
@@ -383,14 +392,21 @@ Test builder
 ------------
 
 This builder (``test-builder``) compiles and starts every Taler component.
-It is run by the ``taler-test`` Gv user.
+The associated worker is run by the ``taler-test`` Gv user, via the SystemD
+unit ``buildbot-worker-taler``.
+
+.. note::
+  the mentioned unit file can be found at ``deployment.git/systemd-services/``
 
 Wallet builder
 --------------
 
 This builder (``wallet-builder``) compiles every Taler component
-and runs the wallet integration tests.  It is run by the ``walletbuilder``
-Gv user.
+and runs the wallet integration tests.  The associated worker is
+run by the ``walletbuilder`` Gv user, via the SystemD unit 
``buildbot-worker-wallet``.
+
+.. note::
+  the mentioned unit file can be found at ``deployment.git/systemd-services/``
 
 Documentation Builder
 ---------------------

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.