Which Docker networking construct is created with the overlay driver and enables container-to-container communication over the physical network infrastructure?

Which Docker networking construct is created with the overlay driver and enables container-to-container communication over the physical network infrastructure?

• A. Bridge
• B. MACVLAN
• C. Overlay
• D. Host Driver

Answer: (C)

Overlay networks are designed for multi-host container communication. Created with the overlay driver, they wrap container traffic and transport it across the physical network so containers on different hosts can talk as if they’re on the same network. This is typically done using tunnels (like VXLAN) over the underlying infrastructure, giving each container its own IP within the overlay and enabling seamless container-to-container communication across the cluster. Bridge networks stay local to a single host, MACVLAN exposes containers on the physical network with their own MAC addresses, and the Host driver places containers in the host’s network namespace, not across multiple hosts.

Overlay networks are designed for multi-host container communication. Created with the overlay driver, they wrap container traffic and transport it across the physical network so containers on different hosts can talk as if they’re on the same network. This is typically done using tunnels (like VXLAN) over the underlying infrastructure, giving each container its own IP within the overlay and enabling seamless container-to-container communication across the cluster.

Bridge networks stay local to a single host, MACVLAN exposes containers on the physical network with their own MAC addresses, and the Host driver places containers in the host’s network namespace, not across multiple hosts.