IP Library Granted Patent US 12,468,522
Granted Patent B2
US 12,468,522 · App. 18/151,273 · Granted Nov 11, 2025

Customizable containerization framework system and method

Inventor: Dhatchana Moorthy Sekar (Bangalore, IN)
Assignee: OPEN TEXT HOLDINGS, INC.
G06F8/65G06F8/71
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,468,522
App. No.
18/151,273
Granted
Nov 11, 2025
Kind
B2
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.

Claims (113)

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.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2025
From: SEKAR, DHATCHANA MOORTHY
To: OPEN TEXT HOLDINGS, INC.
Reel/Frame 070274/0688 →
Continuity (1)
Related Publication 20240231797A1 · Jul 11, 2024
References Cited (70)
US 9195393B1 · Li · 2015 [cited by applicant]
US 9800517B1 · Anderson · 2017 [cited by applicant]
US 9823915B1 · Maloney · 2017 [cited by examiner]
US 10169209B2 · McPherson · 2019 [cited by examiner]
US 10261782B2 · Suarez · 2019 [cited by examiner]
US 10291706B1 · Zhao · 2019 [cited by applicant]
US 10324696B2 · Bhat · 2019 [cited by examiner]
US 10356214B2 · Joshi · 2019 [cited by examiner]
US 10387750B2 · Waugh · 2019 [cited by examiner]
US 10404474B1 · Caceres · 2019 [cited by applicant]
US 10810003B2 · Gainsborough · 2020 [cited by applicant]
US 10868855B2 · Achyuth · 2020 [cited by examiner]
US 10873592B1 · Singh et al. · 2020 [cited by applicant]
US 10877739B1 · Fernandez · 2020 [cited by applicant]
US 10922090B1 · Lieberman · 2021 [cited by applicant]
US 11099882B2 · Rupprecht · 2021 [cited by applicant]
US 11106455B2 · Myers · 2021 [cited by examiner]
US 11201955B1 · Sachdeva · 2021 [cited by applicant]
US 11243868B2 · Li · 2022 [cited by examiner]
US 11307839B2 · Vaddi · 2022 [cited by examiner]
US 11537523B2 · Shuster · 2022 [cited by examiner]
US 11573814B1 · Aithal · 2023 [cited by applicant]
US 11573816B1 · Featonby · 2023 [cited by examiner]
US 11579867B1 · Punathil · 2023 [cited by applicant]
US 11698759B2 · Israni · 2023 [cited by applicant]
US 11726764B2 · Joshi · 2023 [cited by applicant]
US 11762850B2 · Rupprecht · 2023 [cited by applicant]
US 11868769B1 · Dongaonkar · 2024 [cited by applicant]
US 11893382B2 · Tarocchi et al. · 2024 [cited by applicant]
US 11954474B2 · Sree Prakash · 2024 [cited by applicant]
US 11960870B2 · Li · 2024 [cited by examiner]
US 11989586B1 · Srikanta et al. · 2024 [cited by applicant]
US 12020016B2 · Chibon · 2024 [cited by examiner]
US 12039321B2 · Sui · 2024 [cited by examiner]
US 12050690B2 · Sivaswamy · 2024 [cited by applicant]
US 12056511B2 · Tarasov · 2024 [cited by applicant]
US 12126643B1 · Skarphedinsson · 2024 [cited by applicant]
US 12236256B2 · Yu · 2025 [cited by examiner]
US 12282758B2 · Sekar · 2025 [cited by applicant]
US 20050044543A1 · Thomas · 2005 [cited by applicant]
US 20170068676A1 · Jayachandran · 2017 [cited by examiner]
US 20170147335A1 · Parees · 2017 [cited by examiner]
US 20170300311A1 · Vasquez Lopez · 2017 [cited by examiner]
US 20180088926A1 · Abrams · 2018 [cited by examiner]
US 20180095973A1 · Huang · 2018 [cited by examiner]
US 20180341471A1 · Stefanov · 2018 [cited by examiner]
US 20190235897A1 · Goel · 2019 [cited by examiner]
US 20190354389A1 · Du · 2019 [cited by examiner]
US 20200241867A1 · Gainsborough · 2020 [cited by examiner]
US 20200272427A1 · Wang · 2020 [cited by examiner]
US 20200310775A1 · Nyamars · 2020 [cited by examiner]
US 20220197689A1 · Hotinger · 2022 [cited by examiner]
US 20220308861A1 · Frackiewicz · 2022 [cited by examiner]
US 20230025529A1 · Fu · 2023 [cited by examiner]
US 20230087544A1 · Duvur · 2023 [cited by examiner]
US 20230244466A1 · Shah · 2023 [cited by examiner]
US 20240184558A1 · Chen · 2024 [cited by examiner]
US 20240231785A1 · Sekar · 2024 [cited by applicant]
CN 112181587A · 2021 [cited by examiner]
CN 111158737B · 2024 [cited by examiner]
Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 18/151,271, mailed Jul. 19, 2024, 14 pages. [cited by applicant]
Gholami et al., “A Framework for Satisfying the Performance Requirements of Containerized Software Systems Through Multi-Versioning,” ICPT, Edmonton, AB Canada, Apr. 20-24, 2020, pp. 150-160. [cited by applicant]
Song et al., “Towards Transparent and Stealthy Android OS Sandboxing via Customizable Container-Based Virtualization,” CCS, Nov. 15-19, 2021, Virtual Event, Republic of Korea, pp. 2858-2874. [cited by applicant]
Kang et al., “Container and Microservice Driven Design for Cloud Infrastructure DevOps,” 2016 IEEE International Conference on Cloud Engineering, pp. 202-211. [cited by applicant]
Notice of Allowance issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 18/151,271 mailed Nov. 21, 2024, 14 pages. [cited by applicant]
Zhao et al., “Large-Scale Analysis of Docker Images and Performance Implications for Container Storage Systems”, IEEE (2021), pp. 918-930. [cited by applicant]
Poggiani et al., “Live Migration of Multi-Container Kubernetes Pods in Multi-Cluster Serverless Edge Systems”, ACM (2024), pp. 9-16. [cited by applicant]
Morales et al,“Insights on Implementing a Metrics Baseline for Post-Deployment AI Container Monitoring”, ACM (2024), pp. 46-55. [cited by applicant]
Cai et al., “Improving Resource Usages of Containers Through Auto-Tuning Container Resource Parameters”, IEEE (2019), pp. 1-12. [cited by applicant]
Notice of Allowance issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 18/151,271, mailed Mar. 17, 2025, 10 pages. [cited by applicant]