It is important to keep in mind that this is in the experimental channel of Docker, so while it won’t go away, it may change form. Before you ask “but what if you *want* cross-talk?”, containers can have an interface on more than one network - so you can have a container that talks on both netA and netB. Now, containers on netA can talk to one another and not those on netB, and containers on netB can talk to one another and not those on netA. For instance, it is now possible to create more than one bridge network, if you want to isolate groups of containers on a host from one another: docker network create -d bridge netA We hope that as more of Docker is opened up as extension points, the plugin will gain parity with other modes of running Weave.ĭocker now comes with “network” and “service” subcommands, that can be used to manipulate networks - including those run by Weave - more finely than before. However, it’s a double-edged sword: it also means the weave plugin gets a much more narrow view of what is going on (e.g., it doesn’t get told the container name), so it cannot offer the full range of weave features other than by workarounds. And, other tools like Docker Swarm and Docker Compose do not have to make concessions or workarounds for working with Weave - the Weave proxy made this substantially smoother, and the plugin will make it more so still. The weave network interface is added to a container before the container’s entry-point is run, which was a pain point before. Which was not formerly the case, and which is very handy. The Weave plugin gives you a closer integration with Docker: docker inspect -format=’’ $CONTAINER
0 Comments
Leave a Reply. |