Identify Docker 1.9 blockers

[awh]

Docker 1.9 introduces further changes to networking and plugins that impact weave's existing features. These must be identified and filed as issues for resolution in the 1.2 milestone. This involves:

• Test with experimental Docker and record issues. There is an experimental_docker branch in the main repo that adjusts the build and smoketest Vagrantfiles to use the experimental docker repo for such testing
• Investigate other features planned for Docker 1.9

Issues identified so far:

• Docker 1.8+ breaks resolution of unqualified names #1374 - Docker 1.9 breaks resolution of unqualified names
• 666_abuse_start_of_test.sh fails due to docker/docker#17026 #1565 - 666_abuse_start_of_test.sh fails due to docker inspect issue in 1.9.0-rc1 moby/moby#17026 (docker inspect issue in 1.9.0-rc1)

[awh]

I have run the smoke tests using our experimental_docker branch and they all pass, despite #1374 (none of our tests attempt unqualified resolution of container named derived hostnames).

[rade]

moby/moby#16645 provides a glimpse of what is coming up.

[mavenugo]

@rade @awh pls feel free to jump in #docker-network IRC channel and we can discuss on any of the 1.9 related changes.

[rade]

@mavenugo moby/libnetwork#519 causes us major headaches.

[rade]

@awh do the tests pass now, modulo the docker inspect issue?

[awh]

@awh do the tests pass now, modulo the docker inspect issue?

They do.

[awh]

That's with 1.9.0-rc1

[rade]

afaict the inspect issue only affects our tests. and we could "fix" that by moving the dns items first in the inspect format.