-
Notifications
You must be signed in to change notification settings - Fork 712
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.
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
Add docker networks to the Overlay Topology #1584
Conversation
ba04f34
to
4181b29
Compare
4181b29
to
6f0a31d
Compare
r.networks = r.networks[:0] | ||
for i := range networks { | ||
r.networks = append(r.networks, &networks[i]) | ||
} |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
I don't understand how this fixed that issue. Could I have a sentence or two explaining it please? |
Okay explained f2f. Let me think for 20mins. |
As part of the review feedback commit I have changed the registry to store (and walk) images instead of image pointers (we are not modifying them so AFAIU there was no reason to use pointers). |
Try to reproduce the issue (without this PR):
But the edges appeared. |
Okay if you use the weavemesh driver I can indeed reproduce:
|
/cc @rade |
back to fons as didn't fix the above repro. |
Meh, the problem is that the go client for some reason is not filling in the
My bad: https://twitter.com/ThePracticalDev/status/687672086152753152 |
Updating the docker client made it work. |
LGTM |
They both passed tests separately and were no source-line conflicts ... but shit happens.
Fixes #1563