Marc CARRE
a81a873703
Since 1.12.0, `docker inspect -f "{{ .NetworkSettings.Networks.<network>.Aliases }}"` also returns the container's short ID.
See also: https://github.com/docker/docker/blob/master/CHANGELOG.md
> 1.12.0 (2016-07-28)
> Networking
> Add container's short-id as default network alias #21901
Upgrading `docker/docker-py` to 1.9.0-rc2 effectively relaxes test assertions for:
- `tests/integration/network_test.py#test_connect_with_aliases`
- `tests/integration/network_test.py#test_create_with_aliases`
which do something equivalent to:
```
$ docker network create net1
$ docker run --name c1 -d busybox top
$ docker network connect --alias foo --alias bar net1 c1
$ docker inspect -f "{{ .NetworkSettings.Networks.net1.Aliases }}" c1
[foo bar e52bf50e5ee7]
```
allowing us to be consistent with the above change.
In 1.8.1, the below fails as the container's short ID would be present:
```
self.assertEqual(
container_data['NetworkSettings']['Networks'][net_name]['Aliases'],
['foo', 'bar'])
```
In 1.9.0-rc2, the below passes as the container's short ID is ignored:
```
aliases = (
container_data['NetworkSettings']['Networks'][net_name]['Aliases']
)
assert 'foo' in aliases
assert 'bar' in aliases
```
This directory contains integration tests for weave.
Requirements
You need three VMs with docker (>=1.10.0) installed and listening on TCP
port 2375 (see below). You also need to be able to SSH to these VMs without
having to input anything.
The Vagrantfile in this directory constructs three such VMs.
If you are building Weave Net using Vagrant, it is recommended to run the tests from the build VM and not the host.
Running tests
TL;DR: You can run the steps 2. to 7. below with one command:
make PROVIDER=vagrant integration-tests
Detailed steps:
-
Start the build virtual machine (see above article for more details):
vagrant up
-
Start the three testing VMs:
cd test vagrant up
-
SSH into the build VM and go to Weave Net's sources:
cd .. vagrant ssh
you are now on the build VM:
cd ~/weave
-
Compile all code and dependencies:
make make testrunner cd test
-
Upload the weave images from where the
Makefileputs them (weave.tar.gz) to the three docker hosts,docker loadthese, and copies theweavescript over:./setup.sh
-
Run individual tests, e.g.:
./200_dns_test.sh
or run all tests (everything named
*_test.sh):./run_all.sh
-
Stop all VMs:
exit
you are now on your host machine
vagrant destroy -f cd test vagrant destroy -f
Using other VMs
By default the tests assume the Vagrant VMs are used.
To use other VMs, set the environment variable HOSTS to the
space-separated list of IP addresses of the docker hosts, and set the
environment variable SSH to a command that will log into
either (which may just be ssh).
Making docker available over TCP
To make docker listen to a TCP socket, you will usually need to either
run it manually with an option like -H tcp://0.0.0.0:2375; or, for
apt-get installed docker (Ubuntu and Debian), add the line
DOCKER_OPTS="--host unix:///var/run/docker.sock --host tcp://0.0.0.0:2375"
to the file /etc/default/docker, then restart docker.
Updating the GCE test image
When a new version of Docker is released, you willneed to update the GCE test image.
To do this, change the Docker version in run-integration-tests.sh and push the change.
Next build in CircleCI will detect that there is no template for this version of Docker and will first create the template before running tests.
Subsequent builds will then simply re-use the template.