molecule 3.2.4 couldn't resolve module/action 'docker_container'

[jorhett]

I'm more than a bit perturbed that this repeated, clearly defined bug has been closed without any justification #3075

However I was told to open this in discussions, so here I am:

As of this morning all CI jobs with molecule are failing.

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

Ansible and molecule installation method:

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

Results after change to pip3 install molecule[lint,docker]==3.2.3

default > destroy
INFO     Sanity checks: 'docker'
PLAY [Destroy] *****************************************************************
TASK [Destroy molecule instance(s)] ********************************************
changed: [localhost] => (item=ubuntu_2004_js_env)

This is 100% replicable, and is still happening today if I remove the version lock on molecule.

[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