-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Host and Bridge network support in docker stack deploy #16
Conversation
be attached to special networks such as host and bridge. This fix brings in the required changes to make sure the stack file accepts these networks as well. Signed-off-by: Madhu Venugopal <[email protected]> (cherry picked from commit 123f0bfd9894be11cb2da401dad513fd7373d41c)
Signed-off-by: Daniel Nephin <[email protected]> (cherry picked from commit 341703d21e88c55d3489404f9b4fbdcb1e97f98a)
Signed-off-by: Daniel Nephin <[email protected]> (cherry picked from commit d5b505ee8ceda32511359cff674472e349ea3a28)
Seeing error when running
|
Its a flaky test : moby/moby#33337 and resolved via moby/moby#33307. Should we cherry-pick moby/moby#33307 ? |
LGTM all other integration and cli tests are green |
update rpm changelog Upstream-commit: c79e2ca Component: packaging
@thaJeztah @mavenugo Do we need doc changes? I am looking at https://docs.docker.com/compose/swarm/ and https://docs.docker.com/compose/networking/ for reference on how to setup local or bridge network for a service. EDIT: Maybe the note here needs to be updated https://docs.docker.com/compose/compose-file/#network_mode |
@marcusmartins can you check if the changes are already in https://github.com/docker/docker.github.io/tree/vnext-compose (which is the branch for the upcoming release), otherwise open an issue in the docs repository (or perhaps create a PR 😇 ) |
[18.06] Improve scalability of the Linux load balancing Upstream-commit: c863835e99fb5ff4c121066d061e988fffd6c31a Component: engine
Host and Bridge network support in docker stack deploy
update rpm changelog
Cherry-picking from docker/cli#132