v25.1.0 cant find docker driver

[Doumor]

Prerequisites

• This was not already reported in the past (duplicate check)
• It does reproduce it with code from main branch (latest unreleased version)
• I include a minimal example for reproducing the bug
• The bug is not trivial, as for those a direct pull-request is preferred
• Running pip check does not report any conflicts
• I was able to reproduce the issue on a different machine
• The issue is not specific to any driver other than 'default' one

Environment

v25.1.0

(cannot get output, GH workflow)

What happened

Failed to load driver entry point Traceback (most recent call last):
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule/api.py", line 47, in drivers
    pm.load_setuptools_entrypoints("molecule.driver")
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/pluggy/_manager.py", line 421, in load_setuptools_entrypoints
    plugin = ep.load()
             ^^^^^^^^^
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/importlib/metadata/__init__.py", line 205, in load
    module = import_module(match.group('module'))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 999, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule_plugins/containers/driver.py", line 23, in <module>
    from molecule_plugins.podman.driver import Podman as DriverBackend
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule_plugins/podman/driver.py", line 33, in <module>
    from molecule.util import run_command, sysexit_with_message
ImportError: cannot import name 'run_command' from 'molecule.util' (/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule/util.py)

ERROR    Failed to load driver entry point Traceback (most recent call last):
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule/api.py", line 47, in drivers
    pm.load_setuptools_entrypoints("molecule.driver")
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/pluggy/_manager.py", line 421, in load_setuptools_entrypoints
    plugin = ep.load()
             ^^^^^^^^^
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/importlib/metadata/__init__.py", line 205, in load
    module = import_module(match.group('module'))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name, package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 999, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule_plugins/containers/driver.py", line 23, in <module>
    from molecule_plugins.podman.driver import Podman as DriverBackend
  File "/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule_plugins/podman/driver.py", line 33, in <module>
    from molecule.util import run_command, sysexit_with_message
ImportError: cannot import name 'run_command' from 'molecule.util' (/home/runner/micromamba/envs/ansible-ufw/lib/python3.12/site-packages/molecule/util.py)

CRITICAL Failed to find driver docker. Please ensure that the driver is correctly installed.
Error: Process completed with exit code 1.

Reproducing example

Install molecule v25.1.0 and try run molecule test.

Example GH workflow:

      - uses: actions/checkout@v4

      - uses: mamba-org/setup-micromamba@v1
        with:
          micromamba-version: '1.5.8-0'
          environment-file: environment.ci.yml
          init-shell: bash
          post-cleanup: 'all'

      - name: Run Molecule tests
        run: molecule test
        shell: micromamba-shell {0}
        env:
          PY_COLORS: '1'
          ANSIBLE_FORCE_COLOR: '1'
          MOLECULE_DISTRO: ${{ matrix.distro }}


env files:

---
name: ansible-ufw
channels:
  - conda-forge
dependencies:
  - python~=3.12.0
  - pip>=22.2
  - pip:
      - -r requirements.txt
      - -r requirements.ci.txt



ansible-lint
molecule
molecule-plugins[docker]
docker
requests==2.31.0  # pinned to the latest version not breaking Docker SDK
yamllint

[corvus-migratorius]

Same here, pretty much, except I've reproduced this with the latest micromamba release (2.0.5-0), so this doesn't seem to be related to the way micromamba deploys molecule... Also, reproduced on ubuntu2004, ubuntu2204 and ubuntu2404 GithubActions images.

[apatard]

it's probably due to #4359. Either it's handled on molecule side or we'll have to try importing a local copy of run_command into the plugins (as long as it's technically possible, I don't remember if there's a common code in the plugins ...)

[jsf9k]

This is breaking my Molecule testing workflows too, starting today. See, for instance, here.

[Nebucatnetzer]

Same issue with podman.

[apatard]

some more thoughts about what I've said yesterday: the change by itself on molecule side seems simple and logical. I think the right place to fix this issue is in the plugins. I'll try to open a PR to fix the plugins asap.

Can someone please open a bug on the -plugins as the issue is there ?