The scenario now starts its containers with community.docker instead of containers.podman, because docker is the container runtime available on the CI runner. The connection plugin, the login command and the declared collections were adjusted accordingly and the docker SDK for python is installed in the workflow, since the module requires it. Co-authored-by: Copilot <copilot@github.com>
25 lines
649 B
YAML
25 lines
649 B
YAML
---
|
|
|
|
driver:
|
|
name: default
|
|
options:
|
|
managed: true
|
|
login_cmd_template: "docker exec --interactive --tty {instance} bash"
|
|
|
|
platforms:
|
|
- name: certificate-authority-archlinux
|
|
image: docker.io/library/archlinux:base
|
|
- name: certificate-authority-debian
|
|
image: docker.io/library/debian:13
|
|
- name: certificate-authority-fedora
|
|
image: registry.fedoraproject.org/fedora:43
|
|
|
|
provisioner:
|
|
name: ansible
|
|
# The role under test is the project directory itself, so its parent has to be on the roles path.
|
|
env:
|
|
ANSIBLE_ROLES_PATH: "${MOLECULE_PROJECT_DIRECTORY}/.."
|
|
config_options:
|
|
defaults:
|
|
interpreter_python: auto_silent
|