Santhosh Manohar

@dang3r @lnshi Can you add the details on what triggers this issue for you ? Have you able to find any pattern or a way to recreate this issue ?...

@dang3r @dcrystalj @discotroy If you are still having this issue can you check if your host has any udev rules that might rename interface names that start with `vx`. ?...

@mavenugo timeout is because the name can't be resolved in the docker domain. @hustcat Normally what we recommend is to pass external DNS servers through the --dns option in the...

@antoinetran To make sure we understand what issue is clearly, can you provide the details on exactly what the connectivity issue is and what the trigger is ?

@nicklaslof Yes, this is the current behavior. overlay is implemented using vxlan unicast. So handling multicast need some form of packet replication. We are looking into possible options to support...

@dave-tucker Multiple vxlan fdb entries can be created for all zero mac, which is the default destination. This gives an option (with some drawbacks) to handle multicast without the complexities...

@inoc603 If the command you gave is exactly what you used there is a typo in the driver name, `-d ipvaln`

@randunel The limit of 100 concurrent queries was added in 1.11 release. In your test its possible you are hitting it when the DNS resolutions are slow. But first reporters...

@axper You are seeing this issue with 1.10.3 The issue reported in #22144 happens after 1.11 upgrade and that seems to be a DNS resolution issue inside the container. Looks...

@PanJ When I run your app as a standalone container.. `docker run -it --rm -p 80:3000 --name test panj/debugging-simple-server` and access the published port from another host I get this...