-
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
Missing driver.json #3895
Comments
Add ansible collection specific requirements since they are no more installed by default. Also, installing molecule-podman cause error (ansible/molecule#3895)
Add ansible collection specific requirements since they are no more installed by default. Also, installing molecule-podman cause error (ansible/molecule#3895)
for non irc/matrix users, I've written a patch, found in draft PR #3898 It may solve the issue but I'd like to get testing before thinking about getting the PR merged. So, feedback welcome |
Hi! But I am not sure what's going on, also I did not had the problem with python3.9 (only with python3.10 and python3.11). |
@fauust yeah, I found out later that the error was also related to having the "old" plugin modules like molecule-podman or molecule-docker or molecule-vagrant. They should not be used any more and molecule-plugins should be used. Still, it's not fine to break systems for people having both installed. Unused code should not break things. |
If one upgrade from previous molecule versions, and since drivers are now provided by the molecule-plugins, molecule-podman|docker|vagrant packages needs to be removed. See: ansible#3895
Seems like a duplicate of #3883. |
If one upgrade from previous molecule versions, and since drivers are now provided by the molecule-plugins, molecule-podman|docker|vagrant packages needs to be removed. See: - ansible#3883 - ansible#3895
If one upgrade from previous molecule versions, and since drivers are now provided by the molecule-plugins, molecule-podman|docker|vagrant packages needs to be removed. See: - ansible#3883 - ansible#3895
The backtrace is different. While it's triggered by installing molecule[docker] instead of molecule-plugins[docker], molecule should catch this properly. IMHO, a backtrace due to missing driver should not exist and be fixed. |
If one upgrade from previous molecule versions, and since drivers are now provided by the molecule-plugins, molecule-podman|docker|vagrant packages needs to be removed. See: - #3883 - #3895 Co-authored-by: Daniel Ziegenberg <[email protected]>
Issue Type
Molecule and Ansible details
Ubuntu 22.04.2 LTS Server:
https://gist.github.com/konstruktoid/664d9ca3d3f88941ecd69b45b4dd8d81
Molecule installation method (one of):
Ansible installation method (one of):
Desired Behavior
A working
molecule
run.Actual Behaviour
FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.11/site-packages/molecule_docker/driver.json'
https://gist.github.com/konstruktoid/4f5849e65989ecd2421b1aa52132d09a#file-vagrant_log-L38
The text was updated successfully, but these errors were encountered: