Customizable containerization framework system and method

Abstract

Systems and methods for containerization are provided. Various embodiments provide containerization systems and methods deploying an initial container image associated with a startup script, a pre-service script and post-service script. This deployment includes executing the startup script associated with the initial container image, and the executing including copying configuration information for the initial container image into a volume and generating a marker file for the initial container image. The containerization systems and methods also deploying a main container image associated with a startup script. This deployment includes executing the startup script associated with the main container image and copying the configuration information from the volume to a local system. This deployment also includes executing the main container, including executing the pre-service script associated with the initial container image, configuring the main container, executing a main service, and executing the post-service script associated with the initial container image.

What is claimed is: 
     
         1 . A method of containerization, comprising:
 deploying a first initial container image;   executing a first startup script associated with the first initial container image;   copying configuration information associated with the first container image;   deploying a second initial container image;   executing a second startup script associated with the second initial container image;   copying configuration information associated with the second container image;   deploying a main container image;   executing a main startup script associated with the main container image;   copying configuration information associated with the main container image;   generating a marker file for the main container image;   executing a main container associated with the main initial container image comprising:   executing pre-service scripts associated with the first initial container image and the second initial container image;   configuring the main container;   executing a main service;   executing post-service scripts associated with the first initial container image and the second initial container image; and re-executing the main startup script, including identifying that the marker file has been generated.   
     
     
         2 . The method of  claim 1 , further comprising:
 responsive to identifying that the marker file has been generated, re-executing the main container, the pre-service scripts, and the main service.   
     
     
         3 . The method of  claim 1 , further comprising:
 executing an updated main startup script, comprising:
 deleting the configuration information associated with the main container image; 
 copying updated configuration information associated with the main container image; 
 deleting the marker file; 
 generating a new marker file; and 
   re-executing the main container, comprising:
 re-executing the main startup script, comprising:
 deleting the configuration information associated with the main container image; and 
 copying the updated configuration information; 
 
 re-executing the pre-service scripts associated with the first initial container image and the second initial container image; 
 re-executing the main service; and 
 re-executing the post-service scripts associated with the first initial container image and the second initial container image. 
   
     
     
         4 . The method of  claim 3 , wherein the new marker file and the updated configuration information are associated with a new version of the main container image. 
     
     
         5 . The method of  claim 1 , wherein deploying the main container image further comprises:
 executing a variable script associated with the first initial container image; and   executing an environment script associated with the first initial container image.   
     
     
         6 . The method of  claim 1 , further comprising:
 prior to deploying the main container, ensuring that the startup scripts for the first and second initial container images has terminated.   
     
     
         7 . A system for containerization, comprising:
 a processor;   a non-transitory computer-readable medium; and   stored instructions translatable by the processor for executing:
 deploying a first initial container image; 
 executing a first startup script associated with the first initial container image; 
 copying customization information associated with the first startup script; 
 deploying a second initial container image; 
 executing a second startup script associated with the second initial container image; 
 copying customization information associated with the second startup script; 
 deploying a main container image; 
 executing a main startup script associated with the main container image; 
 copying customization information associated with the main startup script; 
 generating a marker file for the main container image; 
 executing a main container associated with the main initial container image comprising: 
 executing pre-service scripts associated with the first initial container image and the second initial container image; 
 configuring the main container; 
 executing a main service; 
 executing post-service scripts associated with the first initial container image and the second initial container image; and re-executing the main startup script, including identifying that the marker file has been generated. 
   
     
     
         8 . The system of  claim 7 , wherein the stored instructions further execute:
 responsive to identifying that the marker file has been generated, re-executing the main container, the pre-service scripts, and the main service.   
     
     
         9 . The system of  claim 7 , wherein the stored instructions further execute:
 executing an updated main startup script, comprising:
 deleting configuration information associated with the main container image; 
 copying updated configuration information associated with the main container image; 
 deleting the marker file; 
 generating a new marker file; and 
   re-executing the main container, comprising:
 re-executing the main startup script, comprising:
 deleting the configuration information associated with the main container image; and 
 copying the updated configuration information; 
 
 re-executing the pre-service scripts associated with the first initial container image and the second initial container image; 
 re-executing the main service; and 
 re-executing the post-service scripts associated with the first initial container image and the second initial container image. 
   
     
     
         10 . The system of  claim 9 , wherein the new marker file and the updated configuration information are associated with a new version of the main container image. 
     
     
         11 . The system of  claim 7 , wherein deploying the main container image further comprises:
 executing a variable script associated with the first initial container image; and   executing an environment script associated with the first initial container image.   
     
     
         12 . The system of  claim 7 , wherein the stored instructions further execute:
 prior to deploying the main container, ensuring that the startup scripts for the first and second initial container images has terminated.   
     
     
         13 . A computer programming product comprising a non-transitory computer-readable medium storing instructions for containerization, the instructions translatable by a processor for:
 deploying a first initial container image;   executing a first startup script associated with the first initial container image;   copying customization information associated with the first startup script;   deploying a second initial container image;   executing a second startup script associated with the second initial container image;   copying customization information associated with the second startup script;   deploying a main container image;   executing a main startup script associated with the main container image;   copying customization information associated with the main startup script;   generating a marker file for the main container image;   executing a main container associated with the main initial container image comprising:   executing pre-service scripts associated with the first initial container image and the second initial container image;   configuring the main container;   executing a main service;   executing post-service scripts associated with the first initial container image and the second initial container image; and re-executing the main startup script, including identifying that the marker file has been generated.   
     
     
         14 . The computer programming product of  claim 13 , the instructions further for:
 responsive to identifying that the marker file has been generated, re-executing the main container, the pre-service scripts, and the main service.   
     
     
         15 . The computer programming product of  claim 13 , the instructions further for:
 executing an updated main startup script, comprising:
 deleting the configuration information associated with the main container image; 
 copying updated configuration information associated with the main container image; 
 deleting the marker file; 
 generating a new marker file; and 
   re-executing the main container, comprising:
 re-executing the main startup script, comprising:
 deleting the configuration information associated with the main container image; and 
 copying the updated configuration information; 
 
 re-executing the pre-service scripts associated with the first initial container image and the second initial container image; 
 re-executing the main service; and 
 re-executing the post-service scripts associated with the first initial container image and the second initial container image. 
   
     
     
         16 . The computer programming product of  claim 13 , wherein deploying the main container image further comprises:
 executing a variable script associated with the first initial container image; and   executing an environment script associated with the first initial container image.   
     
     
         17 . The computer programming product of  claim 13 , wherein the stored instructions further execute:
 prior to deploying the main container, ensuring that the startup scripts for the first and second initial container images has terminated.