text: – Encapsulation and isolation is the first level of security for any containerized 
  
  application. A rogue application does not affect other applications of the hosting 
  environment 
  
  – Container engine inherits default security features from hosting platform 
  
  – Namespace provides an isolated view; for example, file system, mount point, network, 
  
  process ID, and User ID 
  
  **2.3.2 History of containers**
  
  Container seems a latest buzzword with cloud technology. However, a similar concept was 
  used for the first time as early as 1970 where application code was decoupled from UNIX 
  native system calls. 
  
  Overtime, a few more enhancements were made, from stand-alone computer systems to 
  integrated environments. Then, virtualization features evolved with LPAR and workload 
  partition (WPAR) concepts. Although these virtualization features added flexibility, application 
  portability always was a challenge. With containerization, new age software developers 
  received all of the flexibility, portability, and security that they needed. 