Open benchoncy opened 2 years ago
I run into the exact same issue, thanks for opening it
I have the same issue, but I am using registry.redhat.io/ubi8/ubi-init and uasing rotless podman.
]$ molecule --version molecule 4.0.0 using python 3.8 ansible:2.13.1 delegated:4.0.0 from molecule podman:2.0.0 from molecule_podman requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
-- podman --version podman version 4.0.2
-- upgraded molecule to:
$ molecule --version molecule 4.0.1 using python 3.8 ansible:2.13.1 delegated:4.0.1 from molecule podman:2.0.0 from molecule_podman requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
Still same result. Anyone got any solution on this issue ?
I had the same issue.
I resolved it by removing the 'platforms[].command' key as follows:
---
dependency:
name: galaxy
driver:
name: docker
platforms:
- name: instance
image: "geerlingguy/docker-${MOLECULE_DISTRO:-fedora35}-ansible:latest"
#command: ${MOLECULE_DOCKER_COMMAND:-""}
volumes:
- /sys/fs/cgroup:/sys/fs/cgroup:ro
privileged: true
pre_build_image: true
provisioner:
name: ansible
If it helps, my molecule configuration and github pipeline actions used to run it can be found in my github repo here
Curiously, @j020326's suggested fix from https://github.com/geerlingguy/docker-fedora35-ansible/issues/1#issuecomment-1341085187 also worked for molecule in a github actions job which tests a role against Ubuntu 22.04.
Ansible reports container as unreachable when used with molecule and the
command:
value is set.This issue also appears for the fedora34 image. I've also noticed a related issue on the fedora33 repo.
Versions reported by molecule:
OS: Fedora 35
Error received:
Example
molecule.yml
:Steps to replicate:
molecule.yml
withcommand:
set like above.molecule converge
If there is any further information I can provide, do let me know.