From 8e65d89b845be4bd9574275e4d1d059027507884 Mon Sep 17 00:00:00 2001 From: Christian Kotzbauer Date: Sat, 24 Sep 2022 18:56:04 +0200 Subject: [PATCH] doc: update VCN docs Signed-off-by: Christian Kotzbauer --- job-images/vcn/README.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/job-images/vcn/README.md b/job-images/vcn/README.md index 3e046c33..818135c2 100644 --- a/job-images/vcn/README.md +++ b/job-images/vcn/README.md @@ -57,9 +57,6 @@ for the analyze-result, as the Codenotary Cloud is doing this for us. - The Pod-Name, Pod-Namespace and the cluster-name are stored as notarization-attributes. - Environment variables from on the operator prefixed with `SBOM_JOB_` are passed to the job without the prefix. - Use the `SBOM_JOB_VCN_EXTRA_ARGS` env to pass custom flags to the `vcn notarize` command. -- The job-container needs to be privileged, as VCN needs the Docker-Daemon to read the images from. -- VCN currently does not support distroless images and images where no package-manager is installed. -- There's a bug in VCN, that some images could not be notarized (error-messages like `stream copy error: reading from a closed fifo` are appearing) - All bugs or behaviours from VCN which could not be handled by the operator or the `entrypoint.sh` are out-of-scope of this repo. ## Verifying an notarized image (manually)