From 27e79f55407b9e46cee06c97ba53bc3a485f5c03 Mon Sep 17 00:00:00 2001 From: baude Date: Thu, 24 Oct 2019 14:54:57 -0500 Subject: Restructure documentation dir Restructuring the docs dir to make integration with sphinx easier. man pages now exist in docs/source/man and the sphinx make files exists in docs. Signed-off-by: baude --- docs/podman-image-sign.1.md | 57 --------------------------------------------- 1 file changed, 57 deletions(-) delete mode 100644 docs/podman-image-sign.1.md (limited to 'docs/podman-image-sign.1.md') diff --git a/docs/podman-image-sign.1.md b/docs/podman-image-sign.1.md deleted file mode 100644 index 62845e715..000000000 --- a/docs/podman-image-sign.1.md +++ /dev/null @@ -1,57 +0,0 @@ -% podman-image-sign(1) - -## NAME -podman-image-sign - Create a signature for an image - -## SYNOPSIS -**podman image sign** [*options*] *image* [*image* ...] - -## DESCRIPTION -**podman image sign** will create a local signature for one or more local images that have -been pulled from a registry. The signature will be written to a directory -derived from the registry configuration files in /etc/containers/registries.d. By default, the signature will be written into /var/lib/containers/sigstore directory. - -## OPTIONS - -**--help**, **-h** - -Print usage statement. - -**--cert-dir**=*path* - -Use certificates at *path* (\*.crt, \*.cert, \*.key) to connect to the registry. -Default certificates directory is _/etc/containers/certs.d_. (Not available for remote commands) - -**--directory**, **-d**=*dir* - -Store the signatures in the specified directory. Default: /var/lib/containers/sigstore - -**--sign-by**=*identity* - -Override the default identity of the signature. - -## EXAMPLES -Sign the busybox image with the identify of foo@bar.com with a user's keyring and save the signature in /tmp/signatures/. - - sudo podman image sign --sign-by foo@bar.com --directory /tmp/signatures docker://privateregistry.example.com/foobar - -## RELATED CONFIGURATION - -The write (and read) location for signatures is defined in YAML-based -configuration files in /etc/containers/registries.d/. When you sign -an image, Podman will use those configuration files to determine -where to write the signature based on the the name of the originating -registry or a default storage value unless overriden with the --directory -option. For example, consider the following configuration file. - -docker: - privateregistry.example.com: - sigstore: file:///var/lib/containers/sigstore - -When signing an image preceded with the registry name 'privateregistry.example.com', -the signature will be written into sub-directories of -/var/lib/containers/sigstore/privateregistry.example.com. The use of 'sigstore' also means -the signature will be 'read' from that same location on a pull-related function. - -## HISTORY -November 2018, Originally compiled by Qi Wang (qiwan at redhat dot com) -- cgit v1.2.3-54-g00ecf