xsrv VS ansible-role-docker

Yes, OpenLDAP installed from this ansible role

It's dead easy to use TCP/SSL instead of UDP to forward logs. Example rsyslog config

I use rsyslog for that since it's the default in Debian. Configuring forwarding is very simple, a single file in /etc/rsyslog.d/forwarding.conf [1]. Note that this setup uses TLS to encrypt messages so you need to create the relevant certificates (I use self-signed certs). Unencrypted TCP or UDP is simpler, but less secure.

preseed.cfg contains a few basic options needed to setup the OS [1]

I do this with https://github.com/nodiscc/xsrv/tree/master/roles/openldap + https://github.com/nodiscc/xsrv/tree/master/roles/samba. It's just a standalone samba server + LDAP auth for users, no DC or anything like that, so I'm not sure this is what you're looking for.

This ansible role (check the tasks/ directory) gives a good breakdown of what is needed to setup a basic LDAP server and authentication service

I use samba in standalone mode with or without LDAP auth https://github.com/nodiscc/xsrv/tree/master/roles/samba

In this case, yeah sure, go ahead. Looks fine. But is the package really not available at all or rather called differently? (from my perspective packages named equally across a wide range of distros / package managers aren't to common) In the later case you would / could load a var file with a variable which contains distro-specific package names for Redhat and just reference the variable in your install task. (see for example https://github.com/geerlingguy/ansible-role-docker/blob/master/tasks/main.yml#L2 and https://github.com/geerlingguy/ansible-role-docker/tree/master/vars)

To install docker, there's multiple examples to find, I'd start with this role : https://github.com/geerlingguy/ansible-role-docker

You might want to check out https://github.com/geerlingguy/ansible-role-docker

before writing a playbook, check for an existing role to do the work for you

This might not be the answer you're looking for, but geerlingguy.docker is pretty good

I mark bugs, security-related issues, and planned features with appropriate labels, and the stale bot ignores those: https://github.com/geerlingguy/ansible-role-docker/blob/mast...

Not all maintainers do the same. And some even _lock issues_, which I hate, because even closed issues can have a very fruitful discussion long after the issue was originally posted.

As a teaching example, installing your own docker this way might be good.But it would be better to install using a role. One you design yourself, or even better use an existing role like geerlingguy.docker.

I use ansible to setup the docker VMs after provisioning (https://github.com/geerlingguy/ansible-role-docker)

PS. As a slight sidenote, I just wanted to thank you for your (many!) Ansible roles - today I was able to run Docker in Ansible in my side project because of your docker ansible role to investigate Opensearch. Just wanted to say thanks you very much