Well, sort of. Before the Docker networking features, Weave relied on a proxy that intercepts Docker API calls to set up their network before passing requests on to Docker. It was&#x2F;is a workaround for lacking plugin support in Docker, and even after the network plugin support was added it still allows additional functionality that is hard to implement via the plugin mechanism but there is now a Docker network plugin for Weave too.<p>What they&#x27;ve done now if I&#x27;ve understood it correctly, is that they&#x27;ve effectively leveraged that to allow them to intercept Docker API calls, and <i>if</i> that call requests a network provided by a CNI plugin, they call CNI &quot;on behalf of Docker&quot; and then pass on a modified API call to Docker, so you can have Docker&#x2F;Kubernetes&#x2F;Rocket on the same overlay network.<p>&gt; Can containers interoperate regardless of the choice of Docker plugin, or will they only work on a plugin based on the weave proxy?<p>Containers don&#x27;t care what network you configure. Basically Docker will just use a bridge interface, assign IP addresses for a container on that bridge, and optionally expose ports on the host. The Docker networking support lets Docker query an external plugin API to obtain the details to use for a container. Kubernetes and Rocket implements a different plugin API for the same purpose. But in both all of this happens before a container is started.<p>Once it&#x27;s started, the container just sees a an interface bound to a suitable IP, so your containers should not need to care.