# US 2024/0201979 A1 · Updating Running Containers without Rebuilding Container Images

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0201979 A1
- Document ID: US20240201979A1
- Status: Published application
- Kind: A1
- Application number: 18/065,738
- Filed: 2022-12-14
- Published: 2024-06-20
- Earliest claimed: 2022-12-14
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Zhi Li Guan; Peng Hui Jiang; Jun Su; Kun Yang; Cheng Wu
- Web page: https://patentgrep.com/patent/US20240201979A1

## CPC

- G06F 8/656: while running
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Managing container updates is provided. A changed file corresponding to a new version of an application is retrieved from a persistent volume based on a mapping between the new version of the application and the changed file. The changed file corresponding to the new version of the application is loaded in a corresponding file of a running container to update the corresponding file of the running container without redeploying the running container using an updated container image.

## Claims

### Claim 1

A computer-implemented method for managing container updates, the computer-implemented method comprising:
retrieving, by a computer, using a container update manager, a changed file corresponding to a new version of an application from a persistent volume based on a mapping between the new version of the application and the changed file; and
loading, by the computer, using the container update manager, the changed file corresponding to the new version of the application in a corresponding file of a running container to update the corresponding file of the running container without redeploying the running container using an updated container image.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1 further comprising:
receiving, by the computer, using the container update manager, an indication from an application version repository that the new version of the application has been released having an update to a component of the application; and
retrieving, by the computer, using the container update manager, source code of a container image corresponding to the new version of the application having the update to the component of the application from a source code repository.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2 further comprising:
performing, by the computer, using the container update manager, an analysis of the source code of each respective file of the container image corresponding to the new version of the application having the update to the component of the application; and
categorizing, by the computer, using the container update manager, each respective file of the container image as one of a static file or a changed file based on the analysis of the source code of each respective file.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3 further comprising:
determining, by the computer, using the container update manager, whether a given file of the container image is categorized as a changed file; and
uploading, by the computer, using the container update manager, the changed file corresponding to the new version of the application to an application version repository to decrease container image build effort in response to the computer determining that the given file of the container image is categorized as the changed file.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4 further comprising:
reading, by the computer, using the container update manager, information regarding a current configuration of the container image from a container image configuration repository; and
generating, by the computer, using the container update manager, a mapping between the new version of the application and the changed file based on the information regarding the current configuration of the container image.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5 further comprising:
storing, by the computer, using the container update manager, the changed file corresponding to the new version of the application in the persistent volume;
receiving, by the computer, using the container update manager, an input to deploy the container image; and
deploying, by the computer, using the container update manager, the container image on the computer according to the current configuration of the container image in response to receiving the input.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the container update manager is located in the running container that is performing a service corresponding to the application.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the running container is located in the computer.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein the persistent volume is located in an external storage device.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the computer is a worker computer node of a container orchestration environment corresponding to a cloud architecture.

### Claim 11

A computer system for managing container updates, the computer system comprising:
a communication fabric;
a storage device connected to the communication fabric, wherein the storage device stores program instructions; and
a processor connected to the communication fabric, wherein the processor executes the program instructions to:
retrieve, using a container update manager, a changed file corresponding to a new version of an application from a persistent volume based on a mapping between the new version of the application and the changed file; and
load, using the container update manager, the changed file corresponding to the new version of the application in a corresponding file of a running container to update the corresponding file of the running container without redeploying the running container using an updated container image.

### Claim 12 (depends on 11)

The computer system of claim 11, wherein the processor further executes the program instructions to:
receive, using the container update manager, an indication from an application version repository that the new version of the application has been released having an update to a component of the application; and
retrieve, using the container update manager, source code of a container image corresponding to the new version of the application having the update to the component of the application from a source code repository.

### Claim 13 (depends on 12)

The computer system of claim 12, wherein the processor further executes the program instructions to:
perform, using the container update manager, an analysis of the source code of each respective file of the container image corresponding to the new version of the application having the update to the component of the application; and
categorize, using the container update manager, each respective file of the container image as one of a static file or a changed file based on the analysis of the source code of each respective file.

### Claim 14 (depends on 13)

The computer system of claim 13, wherein the processor further executes the program instructions to:
determine, using the container update manager, whether a given file of the container image is categorized as a changed file; and
upload, using the container update manager, the changed file corresponding to the new version of the application to an application version repository to decrease container image build effort in response to determining that the given file of the container image is categorized as the changed file.

### Claim 15

A computer program product for managing container updates, the computer program product comprising a computer-readable storage medium having program instructions embodied therewith, the program instructions executable by a computer to cause the computer to perform a method of:
retrieving, by the computer, using a container update manager, a changed file corresponding to a new version of an application from a persistent volume based on a mapping between the new version of the application and the changed file; and
loading, by the computer, using the container update manager, the changed file corresponding to the new version of the application in a corresponding file of a running container to update the corresponding file of the running container without redeploying the running container using an updated container image.

### Claim 16 (depends on 15)

The computer program product of claim 15 further comprising:
receiving, by the computer, using the container update manager, an indication from an application version repository that the new version of the application has been released having an update to a component of the application; and
retrieving, by the computer, using the container update manager, source code of a container image corresponding to the new version of the application having the update to the component of the application from a source code repository.

### Claim 17 (depends on 16)

The computer program product of claim 16 further comprising:
performing, by the computer, using the container update manager, an analysis of the source code of each respective file of the container image corresponding to the new version of the application having the update to the component of the application; and
categorizing, by the computer, using the container update manager, each respective file of the container image as one of a static file or a changed file based on the analysis of the source code of each respective file.

### Claim 18 (depends on 17)

The computer program product of claim 17 further comprising:
determining, by the computer, using the container update manager, whether a given file of the container image is categorized as a changed file; and
uploading, by the computer, using the container update manager, the changed file corresponding to the new version of the application to an application version repository to decrease container image build effort in response to the computer determining that the given file of the container image is categorized as the changed file.

### Claim 19 (depends on 18)

The computer program product of claim 18 further comprising:
reading, by the computer, using the container update manager, information regarding a current configuration of the container image from a container image configuration repository; and
generating, by the computer, using the container update manager, a mapping between the new version of the application and the changed file based on the information regarding the current configuration of the container image.

### Claim 20 (depends on 19)

The computer program product of claim 19 further comprising:
storing, by the computer, using the container update manager, the changed file corresponding to the new version of the application in the persistent volume;
receiving, by the computer, using the container update manager, an input to deploy the container image; and
deploying, by the computer, using the container update manager, the container image on the computer according to the current configuration of the container image in response to receiving the input.
