- strip "Weave" and "Weave Net"
- "Integrating a Host Network with Weave" -> "Integrating with the
Host Network"
- "Configuring Weave to Explicitly Use an IP Range" -> "Allocating IPs
in a Specific Range"
- move "Managing Services in Weave Net" up so it comes after
"Integrating a Host Network with Weave Net", to which it is deeply
related
- move "Adding and Removing Hosts Dynamically" down so it is adjacent
to the other sections which talk about peer connectivity
vendor/github.com/Sirupsen/logrus to latest release 0.10.0
vendor/github.com/appc/cni to latest master
vendor/github.com/boltdb/bolt to latest release 1.2.0
vendor/github.com/coreos/go-iptables to latest release 0.1.0
vendor/github.com/fsouza/go-dockerclient to latest master
vendor/github.com/docker/docker to latest release 1.11.0
vendor/github.com/docker/libnetwork to v0.7.0-dev.6 matching docker 1.11.0
vendor/github.com/docker/machine to latest release v0.7.0
vendor/github.com/google/gopacket to latest master
vendor/github.com/gorilla/context to latest release 1.1
vendor/github.com/gorilla/mux to latest release 1.1
vendor/github.com/hashicorp/go-cleanhttp to latest master
vendor/github.com/miekg/dns to latest master
vendor/github.com/opencontainers/runc to latest release 0.1.0
vendor/github.com/stretchr/testify unchanged at 1.1.3
vendor/github.com/vishvananda/netlink to latest master
vendor/github.com/vishvananda/netns to latest master
vendor/github.com/weaveworks/go-checkpoint unchanged; already at latest on master
vendor/github.com/weaveworks/go-odp to latest master
vendor/github.com/weaveworks/mesh to latest master
vendor/golang.org/x/crypto to latest master
Otherwise, we are risking to leak DNS entries which happens when
ContainerName is passed to `weave reset` and subsequent internal call
to nameserver creates a new entry instead of replacing the old one.
The ContainerID of the new entry is set to ContainerName and in such case
stopping the container will not remove the new entry.
Matthias Radestock