Improve network endpoints order, keep the interfaces order as it whether the container has been restarted or not #43518
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.
[Signed-off-by: DrAuYueng ouyang1204@gmail.com
Currently there is no way to keep the order for network endpoints , when we run a container with --network flag which referred a pre-created network and connect container to other networks one by one, like this:
Show ip info after connect network to container foo:
ip info:
It looks working well, but if restart the container, the interfaces order has been changed, like this:
ip info:
In addition, the default route for container has been changed too.
I would expect the networks to be assigned to interface in order and should be inconsistent after restarting container.
This PR improves network endpoints order, keep the interfaces order as it whether the container has been restarted or not.
Related issue: docker/compose#4645