-
Notifications
You must be signed in to change notification settings - Fork 122
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
docker_image fails to load image from local path #72
Comments
It could be related to that PR, since it was backported to community.general. Which version of the Docker SDK for Python do you have installed on the target machine? |
@felixfontein hope that helps
|
@TalLannder unfortunately not, I need the version of the Docker SDK for Python. Usually you can get it by running |
@felixfontein yeah it might be pretty old, thanks for the guidance
|
@TalLannder indeed, that's old (over four years!). In fact, |
resolved_by_pr #73 |
@felixfontein thanks a lot sir everything works as expected with |
Any version of Docker SDK for Python >= 2.5.0 should work fine, as I found out while working on a fix :) But the PR, it should also work for older versions (though some of the recent improvements we've added won't work then, because it does not report the results from the API / Docker daemon). |
SUMMARY
While using
docker_image
to load an image from local path the step fails with"msg": "Error loading image image_name - 'NoneType' object is not iterable"
. This step works on ansible v2.9.2 but fails on2.10.5
installed via pip and on develop installed from source.playbook step:
Tested on:
Note: I'm not sure but maybe the issue related to PR62
ISSUE TYPE
COMPONENT NAME
ansible_collections/community/general/plugins/modules/docker_image.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
Build basic image and copy to a local path on target machine and try to load it using docker_image.
EXPECTED RESULTS
The image loaded to docker on target machine. Works on ansible 2.9.2
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: