Docker-map

-------
* The :meth:`~dockermap.map.client.MappingDockerClient.pull_images` action also pulls present images by default (i.e.
updates them from the registry). This was optional before, and can be prevented by passing ``pull_all_images=False``,
only pulling missing image tags.
* Internal cleanup of converting input into configuration ids.

-------
* Included main process id in state data, so that implementations can detect a container restart more easily.
* Handling deprecation of the ``force`` argument when tagging images in newer Docker releases. The tag is added
automatically depending on the detected API version.
* Fixed update check of container network mode referring to another container.
* Additional minor bugfix from previous prereleases.

-------
* Added :attr:`~dockermap.map.config.main.ContainerMap.volumes`: Where the Docker host supports it, volumes can now be
configured with additional properties such as driver and options. The original workaround of Docker containers sharing
anonymous volumes no longer applies in this case.
* The default path of volumes in :attr:`~dockermap.map.config.container.ContainerConfiguration.attaches` volumes can now
be defined, by using a dictionary or list of tuples. They no longer have to (but still can) be set in
:attr:`~dockermap.map.config.main.ContainerMap.volumes`.
* Where the Docker host supports named volumes, container-side paths of
:attr:`~dockermap.map.config.container.ContainerConfiguration.uses` items can be overridden, provided that they are
referring to attached volumes created through another container.
* Removed ``clients`` property from :class:`~dockermap.map.config.container.ContainerConfiguration`. It caused too much
complexity in responding to supported client features. In addition, it was likely to break dependency paths.
:attr:`~dockermap.map.config.main.ContainerMap.clients` is however still available.

-------
* :class:`~dockermap.map.client.MappingDockerClient` now wraps all exceptions so that partial results, i.e. actions that
already have been performed on clients. It raises a :class:`~dockermap.map.exceptions.ActionRunnerException`, which
provides information about the client and action performed, partial results through
:meth:`~dockermap.exceptions.PartialResultsMixin.results`, but also the possibility to re-trigger the original
traceback using :meth:`~dockermap.exceptions.SourceExceptionMixin.reraise`.
* Similarly, direct calls to the utility client :class:`~dockermap.client.base.DockerClientWrapper`, such as
:meth:`~dockermap.client.docker_util.DockerUtilityMixin.cleanup_containers` now return a
:class:`~dockermap.exceptions.PartialResultsError`.
* Added :meth:`~dockermap.map.client.MappingDockerClient.signal` method to client.
* Images have been integrated into the dependency resolution. Images of a container and all of its dependencies can
now be pulled with the new command :meth:`~dockermap.map.client.MappingDockerClient.pull_images`.
* Authentication information for the Docker registry can now be added to
:attr:`dockermap.map.config.client.ClientConfiguration.auth_configs` and are considered during login and image pull
actions.
* Added a built-in group ``__all__``, that applies to all containers or even all configured maps on
:class:`~dockermap.map.client.MappingDockerClient`.
* Several adaptions which makes it easier for programs and libraries using the API to evaluate changes.
* More fixes to image dependency check, so that
:meth:`~dockermap.client.docker_util.DockerUtilityMixin.cleanup_images` now works reliably. Removals can also be
forced where applicable.
* Implemented CLI, missing from 0.8.0b1.
* Various bugfixes from 0.8.0b1.

-------
* Added :attr:`~dockermap.map.config.main.ContainerMap.groups`: Generally an action (e.g. startup of containers) can
now be run at once on multiple items. In order to make input easier, groups can be added to a map that refers to
multiple configurations. Dependencies that multiple items have in common will only be followed once.
* Added forced update: Not all differences between the container configuration and an existing instance can be detected
automatically. A parameter ``force_update`` can now trigger an update of particular containers.
* Added :attr:`~dockermap.map.config.main.ContainerMap.networks`: Docker networks can now be configured
on a map. Referring to them in the property :attr:`~dockermap.map.config.container.ContainerConfiguration.networks`
from one or multiple container configurations will create them automatically. The former ``network`` setting has been
renamed to :attr:`~dockermap.map.config.container.ContainerConfiguration.network_mode` for disambiguation.

-----
* More sensible solution of `Issue 15 <https://github.com/merll/docker-map/issues/15>`_, not changing user-defined
link aliases. Doing so could cause name resolution issues.