[FEATURE]: Docker installation role #44

New Issue

2026-10-05T23:31:52+04:00

max commented

2026-10-05 23:31:52 +04:00

🎯 Problem Statement

Currently, docker must be installed manually after deployment, but it's possible to automate it

💡 Proposed Solution

New role to install docker and docker rootless if user wants it

🔄 Alternatives Considered

Alternative A: just use docker installation script (I have it for debian, but not for alpine). User answers the question during the deployment and one of present roles just runs the script. It may be even simpler. The downside is that "basic" apps are mixed with docker, which is rather an advanced thing
Alternative B: combine both approaches. A new role copies the script to the target machine and runs it. This way docker is completely separated from "basic" apps

Main disadvantage here is the script itself, if it fails, it's harder to say what went wrong, also idempotency is partially lost

📸 Screenshots

No response

⚙️ Technical Approach

In case of a new role:

Question and validation task
New role is created
Role runs tasks step by step (update, add repo, install and so on)

If an existing role copies and runs the script:

Question and validation task
One new task in an existing role

New role + script:

Question and validation task
New role is created
Role runs the script

✅ Acceptance Criteria

Docker can be installed on all systems and guests types
User has an option to install rootless docker

🤝 Are you willing to contribute this feature?

Yes, I can contribute

✅ Submission Checklist

I have searched for existing issues (open and closed) that request the same feature
I have explained the problem this feature solves
I have described a concrete solution or direction
I have considered alternatives and explained why they fall short

### 🎯 Problem Statement Currently, docker must be installed manually after deployment, but it's possible to automate it ### 💡 Proposed Solution New role to install docker and docker rootless if user wants it ### 🔄 Alternatives Considered - Alternative A: just use docker installation script (I have it for debian, but not for alpine). User answers the question during the deployment and one of present roles just runs the script. It may be even simpler. The downside is that "basic" apps are mixed with docker, which is rather an advanced thing - Alternative B: combine both approaches. A new role copies the script to the target machine and runs it. This way docker is completely separated from "basic" apps Main disadvantage here is the script itself, if it fails, it's harder to say what went wrong, also idempotency is partially lost ### 📸 Screenshots _No response_ ### ⚙️ Technical Approach In case of a new role: - Question and validation task - New role is created - Role runs tasks step by step (update, add repo, install and so on) If an existing role copies and runs the script: - Question and validation task - One new task in an existing role New role + script: - Question and validation task - New role is created - Role runs the script ### ✅ Acceptance Criteria - [ ] Docker can be installed on all systems and guests types - [ ] User has an option to install rootless docker ### 🤝 Are you willing to contribute this feature? Yes, I can contribute ### ✅ Submission Checklist - [x] I have searched for existing issues (open and closed) that request the same feature - [x] I have explained the problem this feature solves - [x] I have described a concrete solution or direction - [x] I have considered alternatives and explained why they fall short

max added the enhancement label 2026-10-05 23:31:52 +04:00

max self-assigned this 2026-10-05 23:31:59 +04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: max/vmn-ansible#44