… and Jammy

These platforms do not provide systemd-resolved.

Docker bind mounts a file from the host to /etc/resolv.conf.  This is
inconvenient for us, since we need to create a symlink at
/etc/resolv.conf.  At the same time, we don't want to break DNS.  The
playbook being imported contains a workaround for this situation.

We must start the service to populate the files in
/run/systemd/resolve/, before we can create the /etc/resolv.conf.

This functionality from pytest-testinfra is currently broken.  See
pytest-dev/pytest-testinfra#757 for more details.  Once
pytest-dev/pytest-testinfra#754 has been merged and a new release of
pytest-testinfra is created the Service.exists line can be restored.

…he symlink

/run/systemd/resolve/stub-resolv.conf is a symlink to
/run/systemd/resolve/resolv.conf in AL2023, so in this case the
/etc/resolv.conf symlink resolves to the former not the latter.

For some reason ansible-lint does not know about the existence of
ansible.posix.mount unless ansible itself is added as an extra
dependency.  I believe this is because ansible is not installed when
ansible-lint is installed.

The comment explains why ansible must be added as an additional
dependency for the ansible-lint linter.

Co-authored-by: dav3r <[email protected]>

Co-authored-by: dav3r <[email protected]>

Note that this entails installing dnsutils in the Molecule prepare
stage so that dig is available when the Molecule tests are run.

Co-authored-by: Nick <[email protected]>

Co-authored-by: Nick <[email protected]>

Co-authored-by: Nick <[email protected]>

…role

Co-authored-by: Nick <[email protected]>