anchor.diff:  tomcat:
     image: tutum/tomcat:7.0
     exposedPorts: [8089/tcp]
  -  await: 
  +  await:
       strategy: native
   ----
   
  
positive.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_.
  
  === 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:
  
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_.
  