Add support for Custom Network and Network Alias settings #3793
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add support for Custom Network and Network Alias settings. It's useful when running more that two containers that should communicate via local network.
Implementation details
This patch provide two new configuration variables:
ECS_OVERRIDE_BRIDGE_NETWORK_NAME
- when set, all containers created with NetworkType bridge will be set to this network name. This is equivalent of--net <name>
parameter ofdocker run
commandECS_ADD_CONTAINER_NAME_AS_NETWORK_ALIAS
- when set to true, and when container is using custom network - then container name will be assigned as a network alias. This is equivalent of--network-alias <container-name>
parameter ofdocker run
command.Testing
New tests cover the changes: no
Description for the changelog
Enhancement - Create containers in a custom network and register their name as network alias
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.