Worker Node Image Snapshots for Faster Container Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The delay in provisioning new containers due to the time-consuming process of pulling container images from remote repositories during instantiation in cloud computing systems leads to increased downtime and network bandwidth usage.

Innovation Solution

A method of continuously scanning and analyzing existing worker nodes to predict which container images will be needed for new nodes, creating a snapshot of these images and storing them locally, allowing for immediate provisioning without relying on remote repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If container images are pulled from remote repositories during container instantiation, then container images can be updated and accessed from a centralized source, but the provisioning time increases and network bandwidth is consumed

Engineering Contradiction:
Improvecontainer image availabilityVSAvoidprovisioning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by scanning existing worker nodes and caching their container images before new nodes are provisioned. The image scanner identifies container images from running containers and the image builder creates a manifest with these images, allowing new worker nodes to be provisioned faster without waiting for remote repository pulls.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a local copy of container images by scanning existing worker nodes and building a manifest that includes these images. This local copy is then used to provision new worker nodes, eliminating the need to pull images from remote repositories and significantly reducing provisioning time.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If container images are pulled from remote repositories during container instantiation, then container images can be fetched on-demand, but network bandwidth usage increases

Engineering Contradiction:
Improveimage fetching flexibilityVSAvoidnetwork bandwidth usage
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by scanning existing worker nodes and caching their container images before new nodes are provisioned. The image scanner identifies container images from running containers and the image builder creates a manifest with these images, allowing new worker nodes to be provisioned faster without waiting for remote repository pulls.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a local copy of container images by scanning existing worker nodes and building a manifest that includes these images. This local copy is then used to provision new worker nodes, eliminating the need to pull images from remote repositories and significantly reducing provisioning time.

Inventive Principle:
Principle #26Copying

3Productivity

If container images are cached locally before provisioning, then provisioning speed increases, but the system complexity increases due to scanning and analysis processes

Engineering Contradiction:
Improveprovisioning speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the container image management process into distinct components: an image scanner that identifies container images from running containers, an image builder that creates a manifest with these images, and a worker node provisioner that uses the manifest for provisioning. This segmentation allows each component to perform its specific function independently, managing complexity while improving productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary manifest file that serves as a mediator between the scanned container images and the new worker nodes. The manifest includes a list of container images and their tags, providing a structured interface that simplifies the provisioning process and reduces direct system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4361797B1Intelligent preloading of vms for container orchestration platforms
Publication Date: 2026.03.11 RED HAT LLC
  • EP4361797B1 patent drawingFigure 1
  • EP4361797B1 patent drawingFigure 2
  • EP4361797B1 patent drawingFigure 3

AI summary

A method of generating container image snapshots includes scanning one or more worker nodes of a container cluster to generate an image set describing container images loaded onto the one or more worker nodes. The method also includes analyzing, by a processing device, the image set to generate an image manifest comprising at least some of the container images in the image set. The method also includes generating a snapshot from the image manifest, wherein the snapshot describes a set of container images to be used to build a new worker node. The method also includes storing the snapshot in a local memory of the container cluster. The method also includes, responsive to an instruction to provision the new worker node, loading the set of container images from the local memory to the new worker node and building a container for each of the container images in the set.