anchor.diff:  
   It does not seek to replace or abstract Docker.
   
  -To start using SimplePaaS, install Docker.
  +To start using SimplePaaS, install Docker and the unix utility, socat.
   
   Build the SimplePaaS images into your local image repo.
   
  
positive.code: Each folder should contain a build.sh script that will execute whatever build steps are necessary.
  Build tools should be bootstrapped by this script and not assumed to be installed. (eg, using gradlew)
  
  The Artifact created must be TBD
  
  ### Container 
  
  Each Micro Service will be bundled into a container for deployment into SimplPaaS.  This process of bundling is 
  managed via a Dockerfile.
  
  Each container folder must contain a Dockerfile, and a unittest.sh
  
  The unittest.sh should run any and all infrastructure tests on this single container, for example using Vulcan Infrastructure
  Specifications.
  
  The unittest.sh should generate JUnit compatible result XMLs to output/ and pass through the exit result.
  
  The Dockerfile should contain the normal information to build the container, plus some meta data to indicate
  the required/ provided service dependencies
  
negative.code: build.sh
  ```
  
  The SimplePaaS command line tool, `sp` is available for interacting with a SimplePaaS installation.
  To install the platform, run `sp devinit`, this will install the minimal set of services to act as a PaaS on a single node.
  
  These components allow you to take existing Docker images, as normal, and securely deploy them to 
  the local Docker with declarative Service Injection, via the API.
  
  ## Component Structure
  
  