docs: Adding info re container signatures

Updating docs to reflect container signatures

Fixes #1337

Signed-off-by: Dave Hay <david_hay@uk.ibm.com>
This commit is contained in:
Dave Hay
2021-07-21 09:25:32 +00:00
committed by Miloslav Trmač
parent ce2f64c946
commit ec73ff3d91
3 changed files with 14 additions and 5 deletions

View File

@@ -8,7 +8,9 @@ skopeo\-standalone\-verify - Verify an image signature.
## DESCRIPTION
Verify a signature using local files, digest will be printed on success.
Verify a signature using local files; the digest will be printed on success. This is primarily a debugging tool, useful for special cases,
and usually should not be a part of your normal operational workflow. Additionally, consider configuring a signature verification policy file,
as per containers-policy.json(5).
_manifest_ Path to a file containing the image manifest
@@ -27,8 +29,12 @@ $ skopeo standalone-verify busybox-manifest.json registry.example.com/example/bu
Signature verified, digest sha256:20bf21ed457b390829cdbeec8795a7bea1626991fda603e0d01b4e7f60427e55
```
## NOTES
This command is intended for use with local signatures e.g. OpenPGP ( other signature formats may be added in the future ), as per containers-signature(5). Furthermore, this command does **not** interact with the artifacts generated by Docker Content Trust (DCT). For more information, please see [containers-signature(5)](https://github.com/containers/image/blob/main/docs/containers-signature.5.md).
## SEE ALSO
skopeo(1), containers-signature(5)
skopeo(1), containers-signature(5), containers-policy.json(5)
## AUTHORS