container dns name resolution does not work when connecting a running container to an overlay network #19376
Labels
area/networking
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
priority/P0
Urgent: Security, critical bugs, blocking issues. drop everything until this issue is addressed.
Milestone
Seems like dns name resolution does not work for containers that were connected to an overlay network using
network connect
. See last docker exec ping commands... t1 ping to t2 does not work, t1 ping to t2's ip works, t3 ping to t4 works, and t4 to t2 worksThe text was updated successfully, but these errors were encountered: