Container Image Layer Rebasing via Repository Strategy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Containers, which are meant to be rebuilt rather than maintained and updated, become outdated and vulnerable to security risks as they are kept running for longer than intended, especially when tools like Kubernetes or OpenShift are not deployed due to high overhead costs.

Innovation Solution

The method involves performing a rebase action on the image layers of a container instead of rebuilding the entire container, by updating the base layer and integrating it with the upper layers, thereby creating rebased layers that can be stored and reused to update other containers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of stationary object

If containers are kept running for longer periods, then operational continuity is maintained, but security vulnerabilities increase due to outdated image layers

Engineering Contradiction:
Improvecontainer runtime durationVSAvoidsecurity vulnerability risk
Core Design Contradiction:
Duration of action of stationary objectVSReliability

Solution Approach 1:

The system performs preliminary actions by monitoring for new base image availability and proactively rebasing container image layers before security vulnerabilities can Exploit the running container. The method detects new base images, downloads them, and integrates them with existing container layers to create updated container images, thereby preventing security risks before they materialize.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the entire container is rebuilt to update image layers, then security vulnerabilities are eliminated, but computational and networking resources are excessively consumed

Engineering Contradiction:
Improvesecurity update completenessVSAvoidcomputational and networking resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The container image is segmented into distinct layers (base layer, application layer, etc.), allowing selective updating of only the necessary base layer components rather than rebuilding the entire container. This segmentation enables the system to download and integrate only the new base image with existing upper layers, significantly reducing computational and networking resource consumption while maintaining security updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The method extracts and updates only the specific base layer components that contain security vulnerabilities or need updating, rather than extracting and replacing the entire container. By isolating and updating only the necessary image layers, the system reduces resource consumption while achieving complete security updates.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If container image layers are updated frequently, then security vulnerabilities are reduced, but network congestion and power consumption increase

Engineering Contradiction:
Improvesecurity vulnerability mitigationVSAvoidnetwork congestion and power consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary monitoring and detection of new base image availability before initiating updates. By detecting new base images in advance and preparing them locally, the system reduces the frequency and intensity of network operations during actual container updates, thereby reducing network congestion and power consumption while maintaining security updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The method creates local copies of new base images and stores them in a local repository before integrating them with container layers. This copying approach allows the system to perform updates using local resources rather than repeatedly downloading from remote repositories, significantly reducing network congestion and power consumption while maintaining frequent security updates.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP4258106B1Rebasing image layers utilising a repository-based strategy
Publication Date: 2025.04.09 RED HAT INC
  • EP4258106B1 patent drawingFigure 1
  • EP4258106B1 patent drawingFigure 2A~2B
  • EP4258106B1 patent drawingFigure 3

AI summary

A system and method of performing a rebase action to image layers of a container. The method includes receiving a first indication that an image update of a first container is available. The first container includes a base layer and one or more first layers. The method includes updating, in response to receiving the first indication, the base layer based on the image update to create an updated base layer. The method includes rebasing, by a processing device using the updated base layer, the one or more first layers to create one or more rebased first layers. The method includes the storing the one or more rebased first layers in a repository to be reused to update a second container.