-
Notifications
You must be signed in to change notification settings - Fork 880
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
Overlay mac cleanup issue on IP reuse #1934
Comments
I guess we are facing the same problem on one of our Docker hosts. Is there a possible (manual) workaround? Log outputThere are thousands of these messages.
And there are these messages in between:
Docker versionClient: Server: |
After a restart of the container which is connected to the network
Oh just to mention: we are using a lot of virtual ip addresses on this host because on this host we are running our border controller which routes the traffic from the outside LAN/WAN to the overlay services. |
There seem to be a race condition where the IP reuse brings the overlay namespace with wrong configuration.
The following log shows the issue:
The first container (leaving on a remote node) is c987bed674d82784df8000eed19f7890a633dede5461fac4595c4cf0e250d2ea that gets created and added to the peerDB:
After some time it goes down
Locally while the deletion is happening another container is spawned and reuses the IP because now is free
At this point when the peerDelete fetches the entry in the DB this one changed:
For this reason there would not be any namespace configuration change or deletion: https://github.com/docker/libnetwork/blob/master/drivers/overlay/peerdb.go#L407
So the internal namespace is still holding the wrong config:
After that the entry is garbage collected the proper config has to be:
The text was updated successfully, but these errors were encountered: