anchor.diff:  
   The format is `-p hostPort:containerPort`. This option maps container ports to host ports and allows other containers on our host to access them.
   
  -.More Information about port mapping
  +.Docker Port Mapping
   [NOTE]
   ===============================
   Port exposure and mapping are the keys to successful work with Docker.
  
positive.code: 972f51cc8422eec0a7ea9a804a55a2827b5537c00a6bfd45f8646cb764bc002a
  ----
  
  `-d` runs the container in a detached mode.
  
  The output is the unique id assigned to the container. Check the logs as:
  
  
negative.code: 
  When Docker starts, it creates a virtual interface named ``docker0'' on the host machine. It randomly chooses an address and subnet from the private range defined by RFC 1918 that are not in use on the host machine, and assigns it to docker0. Docker made the choice 172.17.0.1 in this example.
  
  But ``docker0'' is no ordinary interface. It is a virtual Ethernet bridge that automatically forwards packets between any other network interfaces that are attached to it. This lets containers communicate both with the host machine and with each other, and nothing more.
  
  Speaking, by default Docker containers can make connections to the outside world, but the outside world cannot connect to containers. This get's another layer of indirection, if you are using boot2docker on for example Mac or Windows. In this case, we don't even care for the Docker generated IP address, but want to know the address, the host is running at.
  
  