Replies: 5 comments
-
|
As of today, I don't see the value to have that information per layer. The UI should provide the right information that help prioritize security related work. Anything else is just noise to me. |
Beta Was this translation helpful? Give feedback.
-
|
Agree. We can take it out. |
Beta Was this translation helpful? Give feedback.
-
|
Also, looking at the other columns... I think we can leave out also the "Updated" one. This information is not available inside of the container image |
Beta Was this translation helpful? Give feedback.
-
|
Yes, no need for the size. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your clarifications. I think that clarifies things to @xingzhang-suse and the rest of the team. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The current mock of the "container image details" -> "layers grouped view" shows for each layer its size.
Currently this information is not available inside of the
Imageresource produced by SBOMscanner.As you know a container image is made by multiple layers. Right now the backend saves only these details about a continer layer:
apt-get install curl)These information allow the user to know that CVE-123 was originated by running the command
apt-get install curlinside of the layer XYZ.While we could add the size of the layer to the tracked information, I wonder if there's an actual need to show this detail inside of a security product.
Our goal is not to build a "container registry explorer" like Harbor.
CC @davideiori1, @oboc-sts
Beta Was this translation helpful? Give feedback.
All reactions