GitHub user tonybaloney opened a pull request:
https://github.com/apache/libcloud/pull/821
Docker bug fixes
## Bug fixes for the Docker driver
The docker driver was initially tested on v1.21 (1.9.x), Docker API
supports versioning in the URI path now. I've updated the tests with 2 sets of
fixtures, the 1.21 and the 1.24 (latest) API.
For more information on contributing, please see
[Contributing](http://libcloud.readthedocs.org/en/latest/development.html#contributing)
section of our documentation.
### Status
Replace this: describe the PR status. Examples:
- work in progress
- done, ready for review
### Checklist (tick everything that applies)
- [ ] [Code
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
(required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ]
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
(required for bigger changes)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tonybaloney/libcloud docker_updates
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/821.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #821
----
commit 6dfe9404aa8cef4637687d966e39672745a48e93
Author: Anthony Shaw <[email protected]>
Date: 2016-06-24T00:59:16Z
moved docker test fixtures to new location
commit 5101531a5a22d80399cc3c700011516b25b9330a
Author: Anthony Shaw <[email protected]>
Date: 2016-06-24T01:53:11Z
added versioning for docker and split fixtures
commit c24814df7afd6ec694e493d03a53bf59ab7b9de6
Author: Anthony Shaw <[email protected]>
Date: 2016-06-24T02:51:39Z
more fixtures for 1.24
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
