stackhpc / stackhpc/ansible-collection-openstack
os_images: Add check for container engine's usability
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The existing check only verifies whether the engine is present, not necessarily usable by the user executing the role. E.g. Docker client must have privileges allowing to talk to the Docker daemon.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing check in the os_images role and inspect how it currently verifies that the container engine is present. Determine how to validate usability for the user running the role, including access to the Docker daemon; done means the check distinguishes an installed but unusable engine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100