Open dchsueh opened 6 years ago
louisXperiel, the issue you describe in the previous comment is NOT the issue I filed this ticket for
-- edit ; looks like louisXperiel deleted his/her comment
@dchsueh if you have system in faulty condition, can you produce pip freeze
and attach output here?
I tried few times - seem ok. (Note: I never install ansible-container globally but instead use it in virtual env).
I am not sure - at the beginning I had smth similar on ubuntu, when older (or newer) docker-compose was installed, because both have dependency on docker.
I too am running into this issue. What's strange is that this only seems to be happening when using a dockerfile or ansible-container. Manually spawning a container and then executing the commands by typing them in doesn't seem to trigger this issue. I've tested on both CentOS and Alpine Linux and got the same results.
ISSUE TYPE
container.yml
OS / ENVIRONMENT
SUMMARY
Under certain circumstances, the pip install of ansible-container can fail in the 'docker' portion, and I am unsure why. No 'ansible-container' script ends up being created.
I think the cause is some other python library in an incompatible version, but I have not been able to determine what, if so.
STEPS TO REPRODUCE
EXPECTED RESULTS
expect a lot of downloaded packages, and a successful install with 'ansible-container' script present; a good run produces stdout:
ACTUAL RESULTS
a failing run will produce rc==0, stdout:
and stderr:
and no 'ansible-container' script, only the 'conductor' script