README: mention sbom/manifest
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
This commit is contained in:
parent
ebba957fad
commit
c136684426
1 changed files with 5 additions and 2 deletions
|
|
@ -64,10 +64,13 @@ $ sudo image-builder build qcow2 --distro centos-9
|
|||
this will create a directory `centos-9-qcow2-x86_64` under which the
|
||||
output is stored.
|
||||
|
||||
With the `--extra-artifacts=manifest` an
|
||||
With the `--with-manifest` option an
|
||||
[osbuild](https://github.com/osbuild/osbuild) manifest will be
|
||||
placed in the output directory too.
|
||||
|
||||
With the `--with-sbom` option an SPDX SBOM document will be
|
||||
placed in the output directory too.
|
||||
|
||||
### Blueprints
|
||||
|
||||
Blueprints are supported, first create a `config.toml` and put e.g.
|
||||
|
|
@ -93,7 +96,7 @@ $ sudo image-builder build qcow2 --blueprint ./config.toml --distro centos-9
|
|||
### SBOMs
|
||||
|
||||
It is possible to generate spdx based SBOM (software bill of materials)
|
||||
documents as part of the build. Just pass `--extra-artifacts=sbom` and
|
||||
documents as part of the build. Just pass `--with-sbom` and
|
||||
it will put them into the output directory.
|
||||
|
||||
### Filtering
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue