anchor.diff:  
   |dockerContainersFile
   |Instead of embedding YAML string, you can set YAML file location in this attribute.
  +
  +|autoStartContainers
  +|Cube will normally only start a _Docker_ container when it has the same name as an active _Arquillian_ container. That works for things that are _DeployableContainer_'s. For any other service, e.g. a database, you can use the _autoStartContainers_ option to define which _Docker_ containers to automatically start up. The option takes a comma separated list of _Docker_ container ids. e.g. _tomcat7, mysql_
   |===
   
   In next example you can see a whole YAML document with configuration properties.
  
positive.code: tomcat:
    image: tutum/tomcat:7.0
    exposedPorts: [8089/tcp]
    await: 
      strategy: polling
  ----
  
  
negative.code: <2> _Docker_ server version is required.
  <3> _Docker_ server URI is required. In case you are using a remote _Docker_ host or _Boot2Docker_ here you need to set the remote host ip, but in this case _Docker_ server is on same machine.
  <4> A _Docker_ container contains a lot of parameters that can be configured. To avoid having to create one XML property for each one, a YAML content can be embedded directly as property.
  <5> Configuration of _Tomcat_ remote adapter. Cube will start the _Docker_ container when it is ran in the same context as an _Arquillian_ container with the same name.
  <6> Host can be _localhost_ because there is a port forwarding between container and _Docker_ server.
  <7> Port is exposed as well.
  <8> User and password are required to deploy the war file to remote _Tomcat_.
  