anchor.diff:  
   One for injecting the +CubeID+(_containerId_) of the current container created for executing the test, one that injects the +CubeController+ to call lifecycle methods on any cube and one that injects +com.github.dockerjava.api.DockerClient+ instance used to communicate with _Docker_ server.
   
  -CubeID and DockerClient injections only work if the tests are run in client mode, that is by using +@RunAsClient+ or by setting the testable property to false +@Deployment(testable = false)+.
  +DockerClient injection only work if the tests are run in client mode, that is by using +@RunAsClient+ or by setting the testable property to false +@Deployment(testable = false)+.
   
   These can be injected using the +@ArquillianResource+ annotation.
   
  
positive.code: NOTE: This also works in case you set +serverUri+ using +boot2docker+ special word or by using the defaults. Read more about it <<boot2docker, Boot2Docker section>> and <<automatic-resolution, Automatic serverUri resolution section>>. 
  
  In case of using _unix_ socket +dockerServerUri+ is replaced to _localhost_.
  
  == Containerless Server and Docker
  
  
negative.code: <8> Port forwarding is configured using `portBinding` section. It contains a list of `exposedPort` and `port` separated by arrow (_->_). If only one port is provided, *Arquillian Cube* will expose the same port number. In this example the exposed port 8089 is mapped to 8089 and exposed port 8080 is mapped to 8081.
  <9> You can extend another configuration. Any top level element and it's children from the target container-id will be copied over to this configuration, unless they have been defined here already.
  
  As we seen in basic example the definition Arquillian Cube scenarios are described in `dockerContainers` property. 
  But if you want you can avoid using this property by simply creating a file called  `cube` at root of the classpath with same content. 
  _Arquillian Cube_ will read it as it was defined in `arquilllian.xml` file.
  
  [source, yaml]
  .src/test/resources/cube
  ----
  tomcat:
    image: tomcat:7.0
    exposedPorts: [8089/tcp]
    await:
      strategy: polling
    env: [TOMCAT_PASS=mypass, JAVA_OPTS=-Dcom.sun.management.jmxremote.port=8089 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false]
    portBindings: [8089/tcp, 8080/tcp]
  ----
  
  === Await
  
  After a container is started, it starts booting up the defined services/commands.
  