Assign static IPs from upper subnet range#53
Merged
Conversation
When connecting containers to overlay networks, pick IPs from the top of the subnet (broadcast-1, -2, ...) instead of letting Docker IPAM assign from the bottom. Each container gets a deterministic index based on sorted name, preventing IP races between containers on the same node. Already-used IPs across all swarm nodes are skipped via NetworkInspect. Also modernizes helpers using samber/lo and stdlib slices.
firecow
force-pushed
the
assign-high-ips-on-overlay-networks
branch
from
b473c26 to
8954ea8
Compare
Member
Author
|
I ran a test locally, and the containers do get assigned IP's in the top of the range. I'm releasing new version. 
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Uh oh!
There was an error while loading. Please reload this page.