fqcn[action-core]: Use FQCN for builtin module actions (file).
host-krypton.yml:41 Use `ansible.builtin.file` or `ansible.legacy.file` instead.
fqcn[action]: Use FQCN for module actions, such `community.docker.docker_container`.
host-krypton.yml:52 Action `docker_container` is not FQCN.
fqcn[action]: Use FQCN for module actions, such `community.docker.docker_container`.
host-krypton.yml:117 Action `docker_container` is not FQCN.
fqcn[action-core]: Use FQCN for builtin module actions (include_role).
host-krypton.yml:130 Use `ansible.builtin.include_role` or `ansible.legacy.include_role` instead.
We used a similar local role here, in the Freifunk Magdeburg project,
and in personal playbooks. That was moved to an external project,
unified, and reworked, so the external role can act as replacement for
the distributed, redundant copies.
Link: https://github.com/netz39/ansible-role-host-docker
Removes the redundant words "ansible" and "role" from the role name
originating from the Git repo name, and uses the author's name as
namespace instead. This makes it easier to recognize as external role.
Note: the host-wittgenstein recipe already used that new name, but we
did not set it up in requirements, yet. (How did that ever work?)
Link: https://docs.ansible.com/ansible/latest/galaxy/user_guide.html#installing-multiple-roles-from-a-file
Fixes: f4db6fa395 ("Add Ansible setup for wittgenstein")
To install docker on a host you have to put it into that group in
inventory now, instead of adding the role to each host playbook. Idea
is to extend the group docker_host playbook by more docker related
things as for example metrics and monitoring.
Docker does not take the tzdata from host systems, so the
timezone needs to be set individually.
Otherwise dates without explicit timezone information or Z will
be generated or interpreted in the wrong timezone
(such as dokuwiki signatures)
