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
No driver info on overlay network and services not starting #39324
Labels
Comments
#34493 looks similar, but in our situation the behavior happens always. Creating non swarm networks (bridge) works as expected. |
Anything in the daemon and/or system logs that indicates why the network could not be created? |
I 've tried everything but no...I've also tried this:
In the logs I have:
|
doing the same with debug enabled:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Networks created with
overlay
driver in a swarm cluster do not work correctly.Driver
andConfig
options are emptySteps to reproduce the issue:
docker network create --driver overlay test-net
docker network inspect test-net
Describe the results you received:
The network is not working correctly, the services that use the network stay in
new
state forever.Describe the results you expected:
The network to be created correctly ans services starting correctly.
Additional information you deem important (e.g. issue happens only occasionally):
This issue happens systematically on our production cluster (3 managers and 5 workers) and for now we can not create any new network :(
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
journalctl -u docker
does not show any particular errorThe text was updated successfully, but these errors were encountered: