Skip to content

docs: add container image inventory page#1392

Open
pbanerji-sn wants to merge 4 commits into
mainfrom
docs/container-image-inventory
Open

docs: add container image inventory page#1392
pbanerji-sn wants to merge 4 commits into
mainfrom
docs/container-image-inventory

Conversation

@pbanerji-sn

Copy link
Copy Markdown

New documentation page for the Container Image Inventory feature (GA).

Covers:

  • What the inventory is and what problems it solves
  • Setup steps for CLI, registry, and Kubernetes users
  • Grouped and flat views, filtering, search
  • Asset detail tabs (Overview, Issues, Fix Recommendations, Related Projects)
  • Workflow impact by persona
  • Prerequisites, known limitations, and FAQs

Screenshot placeholders use .gitbook/assets/container-inventory-*.png paths — images to be added before merge.

cc @snyk/docs for review

Introduced a comprehensive guide on container image inventory, detailing features, benefits, and usage instructions.
@pbanerji-sn pbanerji-sn requested a review from a team as a code owner June 23, 2026 15:27
@snyk-io

snyk-io Bot commented Jun 23, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Updated image paths in the container image inventory documentation to reflect the correct directory structure.
Updated the section to clarify how the container image inventory works and what challenges it addresses.

Container image inventory is a unified view in the Snyk platform that consolidates all of your container images into a single, manageable list, regardless of where they were scanned.

Instead of navigating a fragmented set of per-scan Projects, you get one authoritative inventory of unique container image assets, each identified by **Registry + Repository + Config Digest**. A single image scanned from a registry import, from the CLI, and a Kubernetes workload all appear as **one asset** with a single, deduplicated issue count.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have identified that an assets true identity is actually: "registry+ rep+ manifest digest+ config digest. We have a ticket to make this change! If we call this out, will it confuse customers ?

I trust your expertise here @pbanerji-sn !

| **Unified asset list** | View all unique container images across your Organization or Group in one place |
| **Deduplicated issue counts** | Issues from multiple scan sources are merged — no more inflated counts |
| **Version grouping** | Group images by repository to explore the full version history of an image |
| **Search and filter** | Filter by registry, image repository, tag, image labels, digest, class, and more |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: maybe split up search and filter since they support different fields?


Container image inventory identifies each unique image by its **Registry + Repository + Config Digest**. Because this identity is based on the immutable config digest rather than a mutable tag, one image scanned from the CLI, a container registry, and a Kubernetes workload appears as a single asset — not three separate Projects.

Issues from all scan sources are merged and deduplicated, so you see one count per unique vulnerability rather than inflated totals from overlapping scans. Images are grouped by repository, giving you a version history view where you can compare build dates, risk scores, and issue counts across digests and spot regressions over time. Each asset also surfaces key metadata — tags, inferred base image, test surface, and last scan date — in one place.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically images are grouped by registry/repo... unsure if it is important to call this out though as the language we use in the UX is group by: image repository


![The ungrouped flat view showing individual assets with all columns.](../.gitbook/assets/container-inventory-flat-view.png)

You can sort the flat view by build date, score, issue count, last scan, class, discovered, or updated — in ascending or descending order — using the sort control in the top-right corner.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add that this will be extended to the grouped view in the future ?


![The filter panel showing all available filter dimensions.](../.gitbook/assets/container-inventory-filter-panel.png)

A **search bar** is also available in the top-right corner. Search matches across asset name, image tags, registry, repository, and digests.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably be more specific here since customers have already raised this. Right now the search feature only does prefix matching, it matches from the start of a string, so typing the middle of a string will not find a match.

A **search bar** is also available in the top-right corner. Search matches across asset name, image tags, registry, repository, and digests.

{% hint style="info" %}
The search bar matches from the beginning of the asset name field. If you cannot find a specific image, try using the **Repository** or **Image tag** filters instead.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

jk!

@bdemeo12 bdemeo12 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Just a few nits!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants