-
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
ansible_connection=docker and async poor performance #302
Comments
I'm not sure how this should be a bug. The connection plugin is working fine. Executing commands in docker containers is a lot slower than executing commands locally, that's why it takes longer. |
(Also this collection does not contain the podman connection plugin, you need to check out the community.podman collection for that.) |
@lucab85 could you please elaborate why exactly this is a bug? If you do not provide more information, I will close this. |
Could we improve the connection performance? I know that performance are influence by so many factors and probably you need to focus also on maintaining compatibility between different version of Docker. |
@lucab85 but how should we improve performace? Can you point out a possible optimization, or way to improve performance? (Also this would be a feature request, not a bug report, since I don't see a bug here.) |
SUMMARY
Hello,
When running the following playbook against a node with
ansible_connection=local
oransible_connection=ssh
, the async works as expected and perform well.When running against a container, using
ansible_connection=docker
oransible_connection=podman
it took more time.The ansible Engineer Team excluded any incompatibility between async and docker connector plugin with pipeline enable on #77046
ISSUE TYPE
COMPONENT NAME
ansible_connection=docker
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
RHEL 8
STEPS TO REPRODUCE
EXPECTED RESULTS
Comparable performance on
ansible_connection=local
andansible_connection=docker
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: