Navid Shaikh
Navid Shaikh
/remove-lifecycle stale
The new update to patch includes fixes for errors caught while linting the markdown files as part of CI. Errors: [ref logs](https://gubernator.knative.dev/build/knative-prow/pr-logs/pull/knative_build-templates/99/pull-knative-build-templates-build-tests/1107875200520687616/), excerpts below ``` I0319 05:23:53.861] ---- Linting the...
There is (meta)data with the image itself which could help atomic scanners to implement different use cases. For example, accessing `Labels` of image under-scan, within atomic scanner for processing. How...
@baude > do you want only on the image name? 1. Image name 2. The dictionary/hash printed by `docker inspect` (only interested in the Labels part right now, but other...
The aim of the scanner is to find out number of layers and metadata of each layer for an image under test, by running `docker inspect` on every parent image....
> The atomic scanner does not hand the docker.socket into the container. we are explicity attempting to not do this. Since we don't want the scanning tool to have privileges,...
Associating JSON should help, should we also be able to achieve the ordering of layers as well? (the order in which they are stacked to build the resulting layered image?)
> What upside do you see coming from running this in a scanner versus outside? Say if I want to get layering information about given container image; number of layers;...
> We can do that but probably as a separate tool or a separate option to atomic scan. +1 for a separate option to atomic scan. > If you could...