You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
After upgrading to Docker 28.0.0 and Compose 2.33.0, overlay networks on worker nodes intermittently fail to be recognized. The issue occurs inconsistently—some networks remain accessible, while others become unreachable under high container/network loads.
This appears to be linked to bulk synchronization delays, particularly when a node exceeds a ~30-second sync threshold. In these cases, affected networks fail to reattach properly, requiring manual intervention. However, some networks remain fully functional regardless of re-composition frequency.
Observed Behavior
Overlay networks intermittently fail on worker nodes.
Networks with high container activity seem more prone to failure.
A temporary workaround—attaching a "dummy" container to the network—restores functionality but is not a viable long-term fix.
Attempts to resolve via network removal, sleep intervals, and --force commands have been unsuccessful.
Expected Behavior
Overlay networks should remain consistently available across all worker nodes, regardless of load or sync timing.
Reproduction Steps
See issue #11894 for reference.
Description
Description
After upgrading to Docker 28.0.0 and Compose 2.33.0, overlay networks on worker nodes intermittently fail to be recognized. The issue occurs inconsistently—some networks remain accessible, while others become unreachable under high container/network loads.
This appears to be linked to bulk synchronization delays, particularly when a node exceeds a ~30-second sync threshold. In these cases, affected networks fail to reattach properly, requiring manual intervention. However, some networks remain fully functional regardless of re-composition frequency.
Observed Behavior
Overlay networks intermittently fail on worker nodes.
Networks with high container activity seem more prone to failure.
A temporary workaround—attaching a "dummy" container to the network—restores functionality but is not a viable long-term fix.
Attempts to resolve via network removal, sleep intervals, and --force commands have been unsuccessful.
Expected Behavior
Overlay networks should remain consistently available across all worker nodes, regardless of load or sync timing.
Reproduction Steps
See issue #11894 for reference.
Environment Details
Docker Version: 28.0.0
Compose Version: 2.33.0
Operating System: Ubuntu 24.04.2 LTS
Kernel Version: 6.8.0-53-generic
Storage Driver: overlay2
Swarm Mode: Active (3 Managers, 3 Nodes)
Additional
Steps To Reproduce
No response
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: