Marc CARRE
16415404c7
test #4 "[ 3e52b548e6df304c61ea5bee0af4b3515e025e7e25152c65ecae3d03c71cf52d == Unable to claim: address 10.32.0.3/12 is already owned by fbe411facc8b657c5850591ab56fc40fb56160d43db0d7363a29ba3edad61134 Unable to claim: address 10.32.0.1/12 is already owned by cf16a2bcdee8dd1ef7e5f0a611127611e67ea734f45d7526678fc3b1fc0c6f5d 3e52b548e6df304c61ea5bee0af4b3515e025e7e25152c65ecae3d03c71cf52d ]" failed: program terminated with code 2 instead of 0 1 of 6 tests failed in 6.499s.
Weave Net - Weaving Containers into Applications
About Weaveworks
Weaveworks is the company that delivers the most productive way for developers to connect, observe and control Docker containers.
This repository contains Weave Net, the first product developed by Weaveworks, and with nearly 5 million downloads to date, it enables you to get started with Docker clusters and portable apps in a fraction of the time compared with other solutions.
Other products from Weaveworks include Weave Scope, a powerful container monitoring tool that automatically maps Docker containers and their interactions, and Weave Flux, a microservice router that automates the access of containers as services.
Weave Net
Weave Net creates a virtual network that connects Docker containers across multiple hosts and enables their automatic discovery. With Weave Net, portable microservices-based applications consisting of multiple containers can run anywhere: on one host, multiple hosts or even across cloud providers and data centers. Applications use the network just as if the containers were all plugged into the same network switch, without having to configure port mappings, ambassadors or links.
Services provided by application containers on the Weave network can be exposed to the outside world, regardless of where they are running. Similarly, existing internal systems can be opened to accept connections from application containers irrespective of their location.