-
Notifications
You must be signed in to change notification settings - Fork 666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v25.1.0 cant find docker driver #4372
v25.1.0 cant find docker driver #4372
Comments
Same here, pretty much, except I've reproduced this with the latest micromamba release ( |
it's probably due to #4359. Either it's handled on molecule side or we'll have to try importing a local copy of |
This is breaking my Molecule testing workflows too, starting today. See, for instance, here. |
Same issue with podman. |
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 ? |
From ansible/molecule#4359 `util.run_command` should now replaced with `app.run_command`. Fixes ansible/molecule#4372 Signed-off-by: Wong Hoi Sing Edison <[email protected]>
From ansible/molecule#4359 `util.run_command` should now replaced with `app.run_command`. Fixes ansible/molecule#4372 Signed-off-by: Wong Hoi Sing Edison <[email protected]>
From ansible/molecule#4359 `util.run_command` should now replaced with `app.run_command`. Fixes ansible/molecule#4372 Signed-off-by: Wong Hoi Sing Edison <[email protected]>
…n_command() From ansible/molecule#4359 `util.run_command()` should now replaced with `get_app(Path()).run_command()`. Fixes ansible/molecule#4372 Signed-off-by: Wong Hoi Sing Edison <[email protected]>
Piling on, this also kills the EC2 plugin
|
Please try with ansible-community/molecule-plugins#294 I had merge the changes to my OBS package https://build.opensuse.org/package/show/home:alvistack/ansible-community-molecule-plugins-23.6.0, able to run molecule v25.1.0 with podman and vagrant driver correctly. |
…n_command() From ansible/molecule#4359 `util.run_command()` should now replaced with `get_app(Path()).run_command()`. Fixes ansible/molecule#4372 Signed-off-by: Wong Hoi Sing Edison <[email protected]>
Prompted by what we discovered in ansible/molecule#4372 Pinning the currently working version of Molecule and Docker SDK.
I've made a release of the -plugins with @hswong3i 's fix today, so it should work again now. |
I confirmed that it's working again for me. |
It would be better to pin down molecule to previous version until we finish a set of major changes related to https://ansible.readthedocs.io/projects/dev-tools/user-guide/test-isolation/ |
@Doumor Can you please update molecule and ansible-compat to latest and check if you still have the problem? |
I am closing this as if its a problem is likely to be with https://github.com/ansible-community/molecule-plugins package, which might need update work with current version of molecule. |
Prerequisites
pip check
does not report any conflictsEnvironment
v25.1.0
(cannot get output, GH workflow)
What happened
Reproducing example
The text was updated successfully, but these errors were encountered: