3.2.4 is broken for docker (at least on Travis)

Issue Type

• Bug report

Molecule and Ansible details

Ansible 3.0 with Molecule 3.2.4

Ansible and Molecule installation method:

pip3 install molecule[lint,docker]

Detail any linters or test runners used:

Desired Behavior

Travis CI job that worked yesterday with 3.2.3 should work.

Actual Behaviour

As of this morning all CI jobs with molecule are failing on Travis. The breakage happened when 3.2.4 appeared. Reverting to 3.2.3 fixes it. I’m still debugging but it’s hard to iterate usefully on Travis 😦

INFO     Sanity checks: 'docker'
ERROR! couldn't resolve module/action 'docker_container'. This often indicates a misspelling, missing collection, or incorrect module path.
The error appears to be in '/home/travis/virtualenv/python3.8.3/lib/python3.8/site-packages/molecule_docker/playbooks/destroy.yml': line 8, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
  tasks:
    - name: Destroy molecule instance(s)
      ^ here

[ssbarnea]

This is not a bug, please use discussions in the future instead of the issue tracker. Installing ansible itself is outside the scope of molecule cli.

[jorhett]

So I’ve discovered the problem. Ansible was installed in the system python, molecule was being installed in user space.

sudo pip3 install ansible
pip3 install molecule[lint,docker]

This used to work in 3.2.3, and stopped working in 3.2.4. Workaround is:

sudo pip3 install ansible
sudo pip3 install molecule[lint,docker]

I fail to understand why molecule will not run from a user-space installation, and why this behavior change was pushed out in a patchfix release?