Docker Image Software Hardware Discovery

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing solutions for discovering installed software and hardware are not applicable to container deployments, as they lack the necessary isolation properties to effectively identify components within containers.

Innovation Solution

The system receives a Docker image, parses it to identify layer files, and uses Software Application Index calls to generate information about relationships between installed software and hardware components, displaying these relationships to the user.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional software/hardware discovery solutions are used, then they work for physical servers and virtual machines, but they are not applicable to container deployments due to relaxed isolation properties

Engineering Contradiction:

Improveapplicability to container deploymentsVSAvoidisolation properties

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary discovery mechanism that operates within the container environment to bridge the gap between the relaxed isolation of containers and the need for reliable software/hardware identification. This intermediary approach enables discovery functionality specifically adapted for container deployments without relying on traditional isolation-based methods.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If containers are used instead of virtual machines, then scalability and speed are improved, but the common discovery solution for virtual machines is not applicable

Engineering Contradiction:

Improvescalability and speedVSAvoidcompatibility with existing discovery solutions

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the discovery approach into container-specific operations that can function independently within the container environment. This segmentation allows the discovery mechanism to operate effectively in containers while maintaining compatibility with the broader system architecture, enabling both scalability and solution applicability.

Inventive Principle:

Principle #1Segmentation

3Measurement precision

If Docker images are parsed to identify layer files, then installed software and hardware components can be identified, but additional processing steps are required

Engineering Contradiction:

Improveidentification of installed componentsVSAvoidparsing and analysis process

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-processing Docker images to identify and catalog layer files and their associated software/hardware components before runtime. This preliminary analysis creates a structured foundation that enables precise component identification during operation while reducing the complexity of real-time discovery operations.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11972252B2Docker installed software/hardware discovery

Publication Date: 2024.04.30 MICRO FOCUS LLC

AI summary

A docker image is received. The docker image is for a container. The container contains files that allow for virtualization of applications that run within the container. The docker image is parsed to identify layer files in the docker image. Installed software components (e.g., installed files) and/or hardware components in the layer files are identified. Software application index calls are made to generate information that identifies relationships between the installed software components and/or hardware components. The relationships between the installed software components and/or hardware components are then displayed to a user.