anchor.diff:  tomcat:
     image: tutum/tomcat:7.0
     exposedPorts: [8089/tcp]
  -  await: 
  +  await:
       strategy: native
   ----
   
  
positive.code:     maximumRetryCount: 1
    capAdd: [a]
    capDrop: [b]
  ----
  <1> The name that are going to be assign to running container. It is *mandatory*.
  <2> Name of the image to be used. It is *mandatory*. If image is not already pulled in _Docker_ server, *Arquillian Cube* will pull it for you.
  
negative.code: <7> After container is up, a list of commands can be executed within it.
  <8> Port forwarding is configured using `portBinding` section. It contains a list of tuple `exposedPort` and `port`. Note that you need to use a CR to separate each pair of elements.
  <9> The exposed port can be bound to specific host and port by using _host_ colon (:) and _port_.
  <10> 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.
  
  === Await
  
  After a container is started, it starts booting up the defined services/commands.
  Depending on the nature of service, the lifecycle of these services are linked to start up or not.
  For example Tomcat, Wildlfy, TomEE and in general all Java servers must be started in foreground and this means that from the point of view of the _Docker_ client, the container never finishes to start.
  But on the other side other services like Redis are started in background and when the container is started you can be sure that Redis server is there.
  To avoid executing tests before the services are ready, you can set which await strategy should be used from *Arquillian Cube* side to accept that _Docker_ container and all its defined services are up and ready.
  
  Currently next await strategies are supported:
  