Make molecule work with ansible-base

Issue Type

• Feature request

Molecule and Ansible details

molecule 3.0.4
   ansible==2.10.0b1 python==3.7

Molecule installation method (one of):

• pip

Ansible installation method (one of):

• pip

Desired Behavior

I have been doing some testing with both ansible-base and ansible, and noticed that Molecule fails to work at all (at least with the default Docker driver) under ansible-base, since it calls the docker_container module directly—which is not part of the base distribution anymore.

It would be nice if Molecule were updated to install the community.general collection and use the community.general.docker_container module if it detects it is not available… somehow.

This is probably a bit of a niche use case, though, but it would be helpful for me so I could test whether a bug affects ansible-base and ansible (2.10 and later), or just ansible-base or ansible (2.10 and later).

Right now I basically can’t use molecule if I’m testing with ansible-base locally.

[yajo]

Thanks for the details @tadeboro. For me, adding this tests/molecule/default/collections.yml file fixed the problem (using ansible-base 2.10 and molecule 3.2.3:

collections:
  - name: community.docker
    version: ">=1.2.0,<2"
  - name: community.general
    version: ">=2,<3"

[tadeboro]

@richm Things are a bit complicated at the moment because the docker Ansible content is in transition between the community.general and the community.docker collections. If you want to use molecule, these are your options right now:

1. molecule + ansible 2.9 -> just works, nothing to do
2. molecule + ansible < 3.0.0 -> just works, nothing to do
3. molecule + ansible >= 3.0.0 -> just works, nothing to do
4. molecule + ansible-base 2.10 -> install community.general < 2.0.0 collection

Once community.general 2.0.0 is out, there will be one more valid combination:

1. molecule + ansible-base 2.10 -> install community.general >= 2.0.0 and community.docker collections

Once molecule drops support for Ansible 2.8, we can start using FQCNs. The situation will then change into this:

1. molecule + ansible 2.9 -> install community.docker
2. molecule + ansible < 3.0.0 -> install community.docker
3. molecule + ansible >= 3.0.0 -> just works
4. molecule + ansible-base 2.10 -> install community.docker

I hope this helps.