Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IPAM mismatch warnings #253

Open
fubarhouse opened this issue Sep 9, 2020 · 0 comments · May be fixed by #254
Open

IPAM mismatch warnings #253

fubarhouse opened this issue Sep 9, 2020 · 0 comments · May be fixed by #254

Comments

@fubarhouse
Copy link
Collaborator

It'd be nice to warn the user if the docker network(s) configured do not match the established network.
This is especially obvious with IPAM, but could be useful for other details as well.
fubarhouse added a commit that referenced this issue Sep 9, 2020
@fubarhouse
#253: Add a warning for IPAM mismatches in docker network.
cbbac1f 
Signed-off-by: Karl Hepworth <karl.hepworth@gmail.com>
fubarhouse added a commit that referenced this issue Sep 9, 2020
@fubarhouse
#253: Add a quick test for IPAM configuration warnings.
fa15e46 
Signed-off-by: Karl Hepworth <karl.hepworth@gmail.com>
@fubarhouse fubarhouse changed the title Docker network diff warnings IPAM mismatch warnings Sep 9, 2020
@fubarhouse fubarhouse linked a pull request Jan 29, 2021 that will close this issue
Open
@fubarhouse fubarhouse linked a pull request Jun 22, 2021 that will close this issue
#253: Add IPAM warnings when configuration doesn't match existing networks #254
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#253: Add IPAM warnings when configuration doesn't match existing networks pygmystack/pygmy
1 participant
@fubarhouse