anchor.diff:  Because Warden relies on a very small subset of the functionality that LXC offers, we decided to create a tool that only implements the functionality we need in under 1k LOC of C code.
   This tool executes preconfigured hooks at different stages of the container start process, such that required resources can be set up without worrying about concurrency issues. These hooks make the start process more transparent, allowing for easier debugging when parts of this process are not working as expected.
   
  -## Container Lifecycle
  +## <a id='container-lifecycle'></a>Container Lifecycle ##
   
   Warden manages the entire lifecycle of containers.
   The API allows users to create, configure, use, and destroy containers.
   Additionally, Warden can automatically clean up unused containers when needed.
   
  -### Create
  +### <a id='create'></a>Create ###
   
   Every container is identified by its _handle_, which Warden returns upon creating it.
  -It is a hexadecimal representation of the IP address that is allocated for the container.
  +The handle is a hexadecimal representation of the IP address that is allocated for the container.
   Regardless of whether the backend providing the container functionality supports networking, Warden allocates an IP address to identify a container.
   
   Once a container is created and its handle is returned to the caller, it is immediately ready for use.
  
positive.code: 
  The optional `CONFIG` parameter is a hash that specifies configuration options used during container creation. The supported options are:
  
  #### bind\_mounts
  
  If supplied, this specifies a set of paths to be bind mounted inside the container.
  The value must be an array. The elements in this array specify the bind mounts to execute, and are executed in order.
  
negative.code: 
  The optional `OPTS` parameter is a hash that specifies options modifying the command being run. The supported options are:
  
  ##### privileged #####
  
  If true, this specifies that the script should be run as root.
  
  #### link HANDLE JOB\_ID ####
  
  Reap the script identified by `JOB_ID`, running in the container identified by `HANDLE`.
  
  Returns a three-element tuple containing the integer exit status, a string containing its `STDOUT` and a string containing its `STDERR`.
  These elements may be `null` when they cannot be determined (e.g. the script could not be executed, was killed, etc.).
  
  #### stream HANDLE JOB\_ID ####
  
  Stream `STDOUT` and `STDERR` of scripts identified by `JOB_ID`, running in the container identified by `HANDLE`.
  
  Returns a two-element tuple containing the type of stream: `STDOUT` or `STDERR` as the first element, and a chunk of the stream as the second element.
  Returns an empty tuple when no more data is available in the stream.
  
  #### limit HANDLE (mem) [VALUE] ####
  
  Set or get resource limits for the container identified by `HANDLE`.
  
  