Eureka on the web
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →Filing growth compares 2021 (7 records) with 2024 (3) — a three-year span. 2024 is the most recent year we treat as complete: publication lags filing by roughly 18 months, so 2025 onwards are still filling in and any growth rate that ends there would understate the field.
Rootless container runtimes let container processes run without root privileges on the host, closing off a class of privilege-escalation risk that has made container security teams nervous since the technology went mainstream. The patent record here is small and recent: 20 published records in scope, with almost no activity before the filing burst that peaked in 2021. That size matters for how the data should be read — this is not a mature, deeply layered field like general container orchestration, it is a narrower slice where a handful of assignees have staked out early claims.
The technology composition leans heavily on core data-processing infrastructure claims (G06F) rather than niche application classes, and the assignee ranking shows one clear leader well ahead of a short tail of single- or double-digit filers. Publication lags filing by roughly 18 months, so the softening visible in 2025 and 2026 in the raw counts understates whatever filing activity is still working through the pipeline.
Pick a task. Every answer cites the patents behind it.
The counts below cover all 20 published records in scope for the search string, spanning receiving offices in the United States, Israel, WIPO (PCT) filings and the EPO.
Filings were essentially flat until 2021, when they reached a peak of 7 for the year. By 2024 — the most recent year that can be treated as complete given publication lag — the count had fallen to 3, a decline of 57% over that three-year window. Readers should not treat 2025 and 2026 figures as evidence of further decline; those years are still filling in.
G06F (electric digital data processing) appears in 90.0% of the 20 records in scope, making it the dominant classification by a wide margin. G06V (image/video recognition) overlaps in 35.0% of records, while G01C, G06K and G06N each appear in only 5.0% — a single record apiece — marking those as thin, exploratory branches rather than established claim territory.
Shares are the percentage of the 20 records in scope. A patent can carry several IPC classes, so the shares add up to more than 100%.
This page is one run against one query. Ask Eureka your own question about containers & orchestration: rootless container runtime patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaThe patent covers an approach for managing container images across runtimes: a first image is downloaded from an image repository, its content data and management data are extracted and separated, and both are stored in an image-sharing file system only when the content data is not already present there. Where the content data is already stored, only the management data is written, avoiding duplicate storage of shared image layers.Filed by International Business Machines Corporation, published 2025-12-02.


| # | Publication no. | Patent title | Citations |
|---|---|---|---|
| 1 | WO2024042508A1 | Geosynchronization of an aerial image using localizing multiple features | 147 |
| 2 | WO2022074643A1 | Improving geo-registration using machine-learning based object identification | 125 |
| 3 | US20240020968A1 | Improving geo-registration using machine-learning based object identification | 101 |
| 4 | US20220374282A1 | Container runtime optimization | 10 |
| 5 | US20220398081A1 | Distroless microservice for small footprint targets | 4 |
| 6 | EP4099163A1 | Method and system for detecting and eliminating vulnerabilities in individual file system layers of a contain… | 4 |
| 7 | US20260133051A1 | Geosynchronization of an aerial image using localizing multiple features | 3 |
| 8 | US20250259069A1 | Systems and methods for secure, segregated reversible machine learning ai | 2 |
| 9 | WO2022253537A1 | Method and system for identifying and addressing vulnerabilities in individual file system layers of a contai… | 2 |
| 10 | US11900173B2 | Container runtime optimization | 2 |
Citation counts favour older filings inside any searched corpus; treat them as a signal of influence on later work, not as a measure of current commercial importance.
Each row carries its publication number; clicking a row searches Eureka by that number.
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →When it has to run inside your own pipeline.
Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.
Browse MCP servers →Three figures from this dataset matter more than the raw counts on their own: how far ahead the leader sits, how the claim space splits by classification, and how citation weight concentrates in a small number of records.
The ranked field covers 7 companies. The leading assignee holds 8 records while the fifth-ranked company holds only 2, indicating that most of the ranked group has filed in the low single digits. This is a small enough field that a new entrant with a well-drafted claim can still shape the landscape.
Filings peaked at 7 in 2021 and had dropped to 3 by 2024, a 57% decline across that span. That pattern is consistent with an early land-grab followed by consolidation onto fewer, more considered filings rather than a technology losing relevance.
Nine in ten of the 20 records in scope carry a G06F classification, covering core electric digital data processing. The 35.0% overlap into G06V image recognition suggests a secondary cluster of filings tying container runtimes to vision or edge-inference workloads, while G01C, G06K and G06N remain single-record branches.
The most-cited records in this corpus are geo-registration and aerial-imaging filings, not core container-runtime patents; the highest-cited runtime-specific record, a container runtime optimization filing, carries 10 citations. That gap is a reminder that citation counts here measure influence within a broader searched corpus, not importance to rootless runtime design specifically.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to containers & orchestration: rootless container runtime patent landscape, with the prior art for and against each one.
The figures above describe what has already been filed. Turning that into a filing or freedom-to-operate decision means going deeper into the specific claims and the white space around them.
The leading assignee's 8 records are the natural starting point for a design-around review, since they set the boundary the rest of the ranked field is filing around.
Explore the portfolio in EurekaG01C, G06K and G06N each hold a single record. A claim drafted precisely in one of these branches faces far less prior art than one filed into the crowded G06F space.
Run a white-space search in EurekaBecause publication lags filing by roughly 18 months, the most recent two years in this dataset understate real activity. Recheck this landscape once those cohorts have caught up.
Set up monitoring in EurekaThe assignee ranking for this dataset returns 7 companies, not a top-50 or top-100 list — it is the full ranked field the data endpoint produces for this search. One company leads with 8 records, while the fifth-ranked company holds only 2, so the field is dominated by one filer with a short tail of smaller portfolios behind it. This is a small enough group that tracking each ranked assignee individually is practical for competitive monitoring.
Filings peaked at 7 in 2021 and had fallen to 3 by 2024, a 57% decline across that three-year span, based on the most recent year that can be treated as complete. Counts for 2025 and 2026 look lower still, but publication lags filing by roughly 18 months, so those years are still filling in and should not be read as continued decline. The honest read is a filing burst around 2021 followed by fewer, more selective filings rather than a technology in retreat.
US12487844B2, assigned to International Business Machines Corporation and published 2025-12-02, covers a method for managing container images across runtimes by separating content data from management data and storing each selectively in a shared file system. The novelty sits in avoiding duplicate storage: management data is written on its own once the underlying content data already exists in the image-sharing file system. Anyone building image-sharing or deduplication logic for container runtimes should read the full claim set before assuming their approach is clear of it.
G06F, electric digital data processing, appears in 90.0% of the 20 records in scope, making it by far the dominant classification. G06V, image and video recognition, overlaps in 35.0% of records, pointing to a secondary cluster connecting container runtimes to vision or edge-inference use cases. G01C, G06K and G06N each appear in only one record apiece, marking those as largely unclaimed branches rather than established territory.
The classification data points to G01C, G06K and G06N as the thinnest branches, each holding only a single record among the 20 in scope, compared with 90.0% density in G06F. That imbalance suggests claims tying rootless runtime mechanisms to navigation, data recognition/presentation, or AI-model-based computing are largely open. A first claim drafted precisely in one of those branches would face far less crowded prior art than one filed into the core G06F space.
Go past this page: query the whole containers & orchestration: rootless container runtime patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.
Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.
Patent data carries inherent limitations: recent filings (typically the most recent 18–24 months) are under-counted due to standard publication lag; counts may be reported at either a patent-family or a patent-record basis and are not always directly comparable; classification, applicant-name, and citation data may contain errors, duplicates, or omissions; and the underlying search query defines and constrains the scope shown. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.
Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, or validity search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. Any patent, commercial, or strategic decision should be verified independently and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.
Machine translation. Assignee and organisation names originally recorded in Chinese, Japanese or Korean have been rendered into English by an AI translation step so that the tables stay readable. These renderings are best-effort and may not match a company's registered English name; the original name is what the underlying patent record carries, and it is what any Eureka query launched from this page uses.