anchor.diff:  <extension qualifier="docker">
     <property name="serverVersion">1.12</property>
     <property name="serverUri">http://localhost:2375</property>
  -  <property name="shouldAllowToConnectToRunningContainers">true</property>
  +  <property name="connectionMode">STARTORCONNECT</property>
     <property name="dockerContainers">
         tomcat:
           #more properties
     </property>
   </extension>
   ----
  +
  ++connectionMode+ is an attribute that can receive three parameters:
  +
  +STARTANDSTOP:: it is the default one if not set any and simply creates and stops all _Docker_ Containers. If a container is already running, an exception is thrown. 
  +STARTORCONNECT:: it tries to bypass the Create/Start Cube commands if a container with the same name is already running, and if it is the case doesn’t stop it at the end. But if container is not already running, Cube will start one and stop it at the end of the execution. 
  +STARTORCONNECTANDLEAVE:: it is exactly the same of _STARTORCONNECT_ but if container is started by Cube it won’t be stopped at the end of the execution so it can be reused in next executions.
  +
  +=== Before Stop Events
  +
  +Sometimes when the tests has finished and container is stopped you want to inspect some data like container console or getting a file from the container to manual inspecting. 
  +In these cases you can configure each container to copy console log or copy a file/s from container to local machine just before container is stopped.
  +
  +Next snippet shows how to copy a directory from container to local disk:
  +
  +[source, yaml]
  +----
  +tomcat_default: 
  +  image: tutum/tomcat:7.0
  +  beforeStop: # <1>
  +    - copy: # <2>
  +      from: /test
  +      to: /tmp
  +
  +    - log: # <3>
  +      to: /tmp/container.log
  +----
  +<1> +beforeStop+ goes into the container section and may contain a list of +copy+ and +log+ elements.
  +<2> +copy+ is used to notify that we want to copy some directories or files form +from+ container location to +to+ local location.
  +<3> +log + is used to notify that we want to copy container log to +to+ local location.
  +
  +In case of +log+ command the standard output and the error output are returned. 
  ++log+ _Docker_ command can receive some configuration paramters and you can set them too in configuration file.
  +
  +[source, yaml]
  +.Example of log parameters
  +----
  +beforeStop:
  +  - log:
  +    to: /tmp/container.log
  +    follow: true
  +    stdout: true
  +    stderr: false
  +    timestamps: true
  +    tail: 10
  +----
  +
  +=== Automatic serverUri resolution
  +
  ++serverUri+ parameter is where you configure the Uri of _Docker_ server. 
  +This parameter is not mandatory and in case you don't set it, _Arquillian Cube_ will use next values:
  +
  +[cols="2*"]
  +|===
  +|Linux
  +|unix:///var/run/docker.sock
  +
  +|Windows
  +|https://boot2docker:2376
  +
  +|MacOS
  +|https://boot2docker:2376
  +|===
  +
  +== Boot2Docker
  +
  +If you are using _boot2docker_ there are some parameters that depends on the installation of the _boot2docker_. 
  +For example _boot2docker_ ip is not _localhost_ and may change every time you start a new _boot2docker_ instance. 
  +Also every time you start _boot2docker_ copies required certificates to home directory of local machine.
  +
  +_Arquillian Cube_ offers some automatic mechanisms to use _boot2docker_ in _Cube_.
  +
  +The first one is that +serverUri+ parameter can contain the word +boot2docker+ like for example +https://boot2docker:2376+. 
  +When _Cube_ is started it will check if the +serverUri+ contains the _boot2docker_ word, and if it is the case it will run the command +boot2docker ip+ to get the ip and substitute the _boot2docker_ sentence to the ip returned by that command. 
  +
  +Note that by default _Arquillian Cube_ assumes that +boot2docker+ command is on +PATH+, but you can configure its location by using +boot2dockerPath+ which is the full location (and program name) of _boot2docker_. 
  +For example +/opt/boot2dockerhome/boot2docker+.
  +
  +_boot2docker_ runs in _https_ and you need to set the certificates path. 
  +These certificates are copied by _boot2docker_ by default at +~/.boot2docker/certs+. 
  +If this propery is not set and the +serverUri+ contains +boot2docker+, then this property is automatically configured to +~/.boot2docker/certs+ so you don't need to worry to set for each environment.
   
   == Building containers
   
  
positive.code: Currently next await strategies are supported:
  
  native:: it uses *wait* command. In this case current thread is waiting until the _Docker_ server notifies that has started. In case of foreground services this is not the approach to be used.
  polling:: in this case a polling (with _ping_) is executed for 5 seconds against all exposed ports. When communication to all exposed ports is acknowledged, the container is considered to be up. This approach is the one to be used in case of services started in foreground.
  static:: similar to _polling_ but it uses the host ip and specified list of ports provided as configuration parameter. This can be used in case of using _Boot2Docker_.
  sleeping:: sleeps current thread for the specified amount of time. You can specify the time in seconds or milliseconds.
  
  
negative.code: ----
  
  [source, yaml]
  .Example polling using ss command by default
  ----
  tomcat:
    image: tutum/tomcat:7.0
  