os_images: Add check for container engine's usability

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ansible, docker
Domain
devops, infrastructure

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.

Description

enhancement

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.

Dominant language
Jinja
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackhpc/ansible-collection-openstack

All issues in stackhpc/ansible-collection-openstack

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.