generated from ansible-collections/collection_template
-
Notifications
You must be signed in to change notification settings - Fork 111
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 swarm init --data-path-port" #296
Labels
Comments
A quick search of https://docker-py.readthedocs.io/en/stable/api.html and the checked out git repo does not indicate this is supported by Docker SDK for Python. (On the API side, the property is called |
felixfontein
added
docker-plain
plain Docker (no swarm, no compose, no stack)
waiting on Docker SDK for Python support
labels
Feb 8, 2022
felixfontein
added
docker-swarm
Docker Swarm
and removed
docker-plain
plain Docker (no swarm, no compose, no stack)
labels
Apr 24, 2022
This is now supported in docker-py via this PR: docker/docker-py#2987 The collection would need to be updated. |
1 task
ghost
mentioned this issue
Sep 8, 2022
1 task
This was referenced Sep 8, 2022
This was referenced Sep 25, 2022
1 task
This was referenced Oct 20, 2022
This was referenced Oct 24, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
The docker swarm init parameter
--data-path-port
is not supported, at least as I searched I did not find it.ISSUE TYPE
COMPONENT NAME
community.docker_swarm
ADDITIONAL INFORMATION
--data-path-port
can be passed todocker swarm init
to use a different port for the bridge network.Background/use-case:
In our customers setup the port is was already used by another network in VMWare, so we were forced to set the bridge/VXLAN UDP port to a different one using mentioned parameter.
see https://docs.docker.com/engine/reference/commandline/swarm_init/#options
I would expect a YAML like this
The text was updated successfully, but these errors were encountered: