Simple, resilient multi-host containers networking and more.
APACHE-2.0 License
Bot releases are hidden (Show)
Published by awh about 8 years ago
bridge "weave" not present
error #2540/#2541Kubernetes does not currently support rolling upgrades of daemon sets, so you will need to perform the procedure manually:
kubectl apply -f https://git.io/weave-kube
.kubectl delete
; wait for the replacement to begin running before moving on to the next.Published by awh about 8 years ago
Kubernetes does not currently support rolling upgrades of daemon sets, so you will need to perform the procedure manually:
kubectl apply -f https://git.io/weave-kube
.kubectl delete
; wait for the replacement to begin running before moving on to the next.Published by awh about 8 years ago
The recommended method of installation is to use the new kubeadm
tool to stand up your cluster - see this guide for details.
docker network inspect weave
#1803/#2412docker run --net
with plugin #2462Published by awh about 8 years ago
--rewrite-inspect
#2533Published by brb about 8 years ago
weave ps
was occasionally failing to list allocated addresses of containers #2388/#2418/#2445weave launch[-router]
on 4.2 kernel would appear to succeed even if the fast datapath VXLAN UDP port was in use by a different process #2375/#2474ipam
option in the help output of the status
subcommand #2425/#2426--no-dns
parameter #2430weave expose
has not run yet #2471weave launch-plugin
without the router running #2293/#2416create-bridge
subcommand was not enabled in the fast datapath mode #2464/#2466weave setup[-cni]
by initializing the CNI plugin on the launch[-router]
subcommand #2435/#2442create-bridge
subcommand initialize required interfaces #2478-f
flag from the docker tags
command in Makefile #2470--host
parameter of the launch[-router]
subcommand #2347/#2413--trusted-subnets
parameter of the launch[-router]
subcommand #2211/#2415eval $(weave env)
when using the plugin #2450Published by awh over 8 years ago
Installation and Upgrading
Follow the installation instructions to install this latest release of weave. If you're upgrading from an earlier version, see the instructions on upgrading your cluster.
Weave 1.6.0 is fully compatible with Weave 1.5.x, 1.4.x, 1.3.x, 1.2.x and 1.1.x, so it is possible to upgrade clusters incrementally and run mixed versions. If upgrading from Weave 1.0.x, take into account the Weave 1.1.0 upgrading instructions.
Note that all Weave components now apply a policy of --restart=always
, so they will come back again
on reboot. If you have your own start-up script, you should review whether this needs to be updated or disable the policy with --no-restart
.
NB there is a backwards incompatible change to
weave reset
to address an issue where IPAM addresses were not freed if the router was not running at the time of reset. Consequently, the command will now fail if the router is not running; the old behaviour can be obtained withweave reset --force
.Another change in behaviour: networks created via
docker network create --driver=weave
orweavemesh
do not now add a multicast route by default; this was preventing more than one network being used by a container. #1960/#2327
/etc/resolv.conf
in Weave DNS fallback resolution, which is especially important when weave is launched early on system (re)start, prior to the file having been populated #2360/#2364/#2378weave stop-plugin
when containers attached via the plugin still exist #2320/#2331--help
#2318/#2352weave dns-args
output consistent #2197/#2203weave rmpeer
error messages on isolated peers #2057/#2205weave reset
did not relinquish IPAM addresses if router was down #2326/#2332--rm
was specified #2296/#2284-H /var/run/weave/weave.sock
would break #2302/#2333Published by bboreham over 8 years ago
weave launch
if the plugin had not shut down cleanly #2286/#2292weave reset
#2304weave reset
to allow updates to reach peers #2280Published by bboreham over 8 years ago
Documentation for this release is available here.
weave rmpeer
persists the range takeover in case the peer on which it was executed dies subsequently #2238WEAVE_CIDR
in the allocation range now waits instead of erroring if the allocator hasn't finished initialising #2232/#2265weave restart
no longer leaks DNS entries when supplied a container name instead of an ID #2193/#2204weave launch
no longer generates misleading "Unable to claim" warnings for addresses allocated via the Docker network plugin #2194/#2262/#2196weave status ipam
#1876/#2263--log-level
in weave usage #2245/#2250WEAVE_MTU
with fast datapath #2198/#2253Published by bboreham over 8 years ago
Installation and Upgrading
Follow the installation instructions to install this latest release of weave.
Weave 1.5.0 is fully compatible with Weave 1.4.x, 1.3.x, 1.2.x and 1.1.x, so it is possible to upgrade clusters incrementally and run mixed versions. If upgrading from Weave 1.0.x, take into account the Weave 1.1.0 upgrading instructions.
Note that all Weave components now apply a policy of --restart=always
, so they will come back again
on reboot. If you have your own start-up script, you should review whether this needs to be updated or disable the policy with --no-restart
.
--restart=always
#2029weave launch
is now idempotent, making the command easier to use in automated/scripted deployments #1859/#1967weave stop
no longer removes component containers, so now their logs can be read subsequently, and they can be restarted #1937/#1939weave rmpeer
now accepts a list of peers #2044/#2075weave rmpeer
now report on size of transferred range, or reports that nothing was done, rather than returning an error #2058/#2066/#2067weave version
now reports the version that will run next after an upgrade, not the version of an older, stopped, Weave #1827/#1938weave launch
command has malformed peer address #1892/#1924weave attach-bridge
feature to replace undocumented create-bridge
#1955/#1964weave expose
, so a receiver can see the real source address #2147/#2158weave reset
#901/#1866/#1888/#2021/#2037--init-peer-count n
has been rephrased as --ipalloc-init consensus=n
; the old parameter is retained for backward compatibility #2155--ipalloc-init seed
option #1998/#2000/#2155--ipalloc-init observer
option #1743/#1990/#2063/#2134/#2155/#2060weave prime
command ensures that the network has reached a consistent state where IP address allocation has been fully initialised #1994/#1997weave connect
, for the default ipalloc-init consensus
count, which helps to avoid split-brain scenarios during dynamic network formation #1721/#2070/#2139/#2150--no-dns
option #1687/#2099/#2101docker network create
#1806/#1915weave
network into a separate utility #1897/#1901docker run --pid=host
#578/#1982/#1965/#1966multiweave
test harness to work with fast datapath #1589rmpeer
command #2073mesh
library out to its own repository #1889/#1890Published by awh over 8 years ago
Fixes some issues encountered by our users.
Other fixes:
Published by bboreham over 8 years ago
Higher performance for multicast and broadcast traffic when using Weave's Fast Datapath
Other fixes:
docker/libnetwork
IPAM API #1984/#1985Published by awh over 8 years ago
Fixing a rather serious issue that slipped through our preparations for Docker 1.10:
Also one other small fix:
Published by awh over 8 years ago
Preparing for Docker 1.10, plus some bug-fixes.
docker volume ls
after weave stop
, weave stop-plugin
or weave reset
#1934/#1936docker exec
with Weave proxy --rewrite-inspect
enabled #1911/#1917weave ps
to show IP addresses allocated via plugin #1745/#1921weavewait
program in Docker volumes #1757/#1935--no-multicast-route
mode #1942/#1943Published by awh almost 9 years ago
Bug-fixes and minor improvements.
weave launch
returns success when the plugin is running, to avoid failure on reboot #1869weave launch
would exit with error code on docker <1.9 #1851eval $(weave env)
multiple times would break eval $(weave env --restore)
#1824/#1825weave stop
about "Plugin is not running" when plugin is not enabled #1840/#1841weave --local launch
would fail if utility program docker_tls_args
could not be found #1844--trusted-subnets
usage to weave
script #1842weave run
can hang under rare combinations of options #1858Published by bboreham almost 9 years ago
This is a bug-fix release to cover a few issues that came up since the
release of 1.4.0.
$DOCKER_HOST
was set to a TCP socket secured with TLS #1820/#1822--with-dns
option to proxy, which was removed #1810/#1812weave version
show the plugin version #1797/#1813weave launch
show when the a container is restarting #1778/#1814weave launch
fail if the plugin is running, for consistency with router and proxy. #1818/#1819More details in the change log.
Published by bboreham almost 9 years ago
More details below and in the change log.
Installation and Upgrading
Follow the installation instructions to install this latest release of weave.
Weave 1.4.0 is fully compatible with Weave 1.3.x, 1.2.x and 1.1.x, so it is possible to upgrade clusters incrementally and run mixed versions. If upgrading from Weave 1.0.x, take into account the Weave 1.1.0 upgrading instructions.
If you used the plugin from version 1.3.x you may need to modify your startup scripts, since weave launch
now creates a default network called weave
. Note that the plugin container (weaveplugin
) is now run with --restart=always
, so that it is there after a restart or reboot. If you remove this container before removing all endpoints created using --net=weave
, Docker can hang.
Router
weave connect
attempts connection immediately #1714/#1716weave status
and weave status ipam
#1639/#1702--with-dns
option; DNS is on by default #1754/#1781weave
script #1748/#1751/#1753Proxy
$DOCKER_HOST
and Weave proxy socket #1579/#1586/#1689/#1694/#1740--no-detect-tls
#1539/#1679Plugin
Build and Test
Published by awh almost 9 years ago
Highlights
weave
script will fail to pull down images from the hub; if you are unable to upgrade to 1.3.1 immediately you can work around this by running weave --local setup
in conjunction with a compatible Docker client installationInstallation and Upgrading
Follow the installation instructions to install this latest release of weave.
Weave 1.3.1 is fully compatible with Weave 1.3.0, 1.2.x and 1.1.x, so it is possible to upgrade clusters incrementally and run mixed versions. If upgrading from Weave 1.0.x, take into account the Weave 1.1.0 upgrading instructions.
Changes
WEAVE_MTU
to container interfaces, allowing you to configure larger frames for improved performance on networks which support it #1703 / weaveworks/docker-plugin#50 / weaveworks/docker-plugin#51Published by awh almost 9 years ago
Highlights
This release includes a Docker Plugin, so you have the option to use Weave Net that way.
More details below and in the change log.
Installation and Upgrading
Follow the installation instructions to install this latest release of weave.
Weave 1.3.0 is fully compatible with Weave 1.2.x and 1.1.x, so it is possible to upgrade clusters incrementally and run mixed versions. If upgrading from Weave 1.0.x, take into account the Weave 1.1.0 upgrading instructions.
Other changes
_Router_
_Docker API proxy_
_IP Address Allocator_
Published by awh almost 9 years ago
Bug-fix and minor improvements.
weave launch
to fail with a address family not supported by protocol
netlink error in the logs #1599/#1619unknown flow key type 22
error using fast datapath on 4.3 kernel #1594weave expose
that could prevent registration of the given hostname in weaveDNS #1626/#1629host
or container:...
at start rather than create (which is the usual way) #1600/#1608--rewrite-inspect
race on container start #1549/#1616Published by bboreham almost 9 years ago
Highlights
This release introduces the Fast Data Path, which allows Weave networks to operate at near wire-level speeds. This new feature is enabled by default.
Other highlights:
More details below and in the change log.
Installation and Upgrading
Follow the installation instructions to install this latest release of weave.
Weave 1.2.0 is fully compatible with Weave 1.1.x, so it is possible to upgrade clusters incrementally and run mixed versions. If upgrading from Weave 1.0.x, take into account the Weave 1.1.0 upgrading instructions.
(Once upgraded, if you then decide to re-install weave 1.1 take care to run weave reset
before downgrading. Failing that, reboot the machine)
HostConfig
on start
, which is a backward compatibility--log-level=debug
. #1515/#1536/var/run/weave.sock
symlink, which was there for backward/var/run/weave/weave.sock
. #1492/#1495--init-peer-count
values were specified. Previously this couldweave status connections
output. #1178/#1463/#1499weave detach/hide
. This wasdocker run/start
and weave run/attach
when a/etc/hosts
,/etc/hosts
for the container's fully-qualifiedweave dns-add/remove
VERSION
env var to WEAVE_VERSION
, to prevent accidental