Skip to content

Set the bip network value as the subnet#40497

Merged
thaJeztah merged 1 commit intomoby:masterfrom
arkodg:fix-bip-subnet-config
Feb 12, 2020
Merged

Set the bip network value as the subnet#40497
thaJeztah merged 1 commit intomoby:masterfrom
arkodg:fix-bip-subnet-config

Conversation

@arkodg
Copy link
Copy Markdown
Contributor

@arkodg arkodg commented Feb 11, 2020

Dont assign the --bip value directly to the subnet
for the default bridge. Instead use the network value
from the ParseCIDR output

closes #40392

Signed-off-by: Arko Dasgupta arko.dasgupta@docker.com

Dont assign the --bip value directly to the subnet
for the default bridge. Instead use the network value
from the ParseCIDR output

Addresses: moby#40392

Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com>
Copy link
Copy Markdown
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah
Copy link
Copy Markdown
Member

@cpuguy83 ptal

@cpuguy83
Copy link
Copy Markdown
Member

CI is failing due to lint validation from another PR that was merged.

Copy link
Copy Markdown
Member

@cpuguy83 cpuguy83 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah
Copy link
Copy Markdown
Member

Windows docker build is failing for no obvious reason (same as on #40500 (comment))

Perhaps something with those machines, or a Windows update?

Not related to this PR as this doesn't modify Windows code, so I'll go ahead and merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Changing docker0 network with bip option: cannot set .0 as ending ip network address

3 participants