-
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
Docker daemon crash because of libnetwork issue #1572
Comments
Thanks @bvis |
I'll add a portion of the logs to the task description. |
Ahh
Thank you @bvis , I recently fixed this in #1555 and the fix is going to be in docker 1.13 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I don't know if this is the right place to create this issue, but I've seen it seems to be related with libnetwork.
Today I've seen that one of the managers (v1.12.3) of my swarm cluster was not responding. Then I checked the status and it said:
I've not found this reference on any issue but maybe it's something duplicated or fixed on 1.13.
Output of
docker info
:After restarting the daemon, of course.
Output of
docker version
:** System logs **
The text was updated successfully, but these errors were encountered: