infra-bootstrap-tools VS ansible-role-docker

I have started to documents my infra for small projects here if you are interested: https://github.com/xNok/infra-bootstrap-tools

In this article, I will give you a tour of Terraform Cloud and the necessary explanations to get started. This piece is part of a series I created on How to create infrastructure for a small self-hosted project. You can find all the code here: https://github.com/xNok/infra-bootstrap-tools, but this article does not how much prior requirements if it is not being a little bit familiar with Terraform.

I want to remind you that the goal of this tutorial series is to document what I consider the bare minimum for a small self-hosted side project. I invite you to visit my repository for more information: https://github.com/xNok/infra-bootstrap-tools. At this point, we are doing the groundwork of setting up a server to host the application we will deploy later as docker containers.

With a small project spread across several articles, I want to show you what I consider the minimum requirement for a small self-hosted project. I invite you to check my Github repository for other articles and more details about the whole project.

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