generated from ansible-collections/collection_template
-
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
Add support for docker init --data-path-addr
#339
Labels
Comments
chrische
added a commit
to chrische/ansible-collections.community.docker
that referenced
this issue
May 2, 2022
chrische
added a commit
to chrische/ansible-collections.community.docker
that referenced
this issue
May 2, 2022
felixfontein
added a commit
that referenced
this issue
May 9, 2022
#344) * adds data_path_addr option for swarm init and swarm join. (#339) * adds changelog fragment (#339) * adds formatting to changelog entry Co-authored-by: Felix Fontein <[email protected]> * adds version to doc entry in ansible_swarm Co-authored-by: Felix Fontein <[email protected]> * rewrites doc entry to formal language Co-authored-by: Felix Fontein <[email protected]> * Correct docker api version (src: docker api docs) Co-authored-by: Felix Fontein <[email protected]> Co-authored-by: Felix Fontein <[email protected]>
1 task
This was referenced May 14, 2022
Merged
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
--data-path-addr
parameter allows configuration for the Services to be exposed on a different interface as described here:https://docs.docker.com/engine/swarm/networking/#use-a-separate-interface-for-control-and-data-traffic. It is currently missing from the latest
docker_swarm
module https://docs.ansible.com/ansible/latest/collections/community/docker/docker_swarm_module.html#ansible-collections-community-docker-docker-swarm-moduleThe Docker SDK for Python supports the param in the
init()
andjoin()
functions (asdata_path_addr
) and in the low-level APIsThe text was updated successfully, but these errors were encountered: