From 5d522431c6ad5daf03027c86e25abda6363570d8 Mon Sep 17 00:00:00 2001 From: Abhijeet Kasurde Date: Thu, 18 May 2023 16:44:24 -0700 Subject: [PATCH] Correct markdown in docs Signed-off-by: Abhijeet Kasurde --- docs/source/markdown/podman-image-sign.1.md.in | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/source/markdown/podman-image-sign.1.md.in b/docs/source/markdown/podman-image-sign.1.md.in index 2a49976741..3aac6439a0 100644 --- a/docs/source/markdown/podman-image-sign.1.md.in +++ b/docs/source/markdown/podman-image-sign.1.md.in @@ -38,9 +38,11 @@ Override the default identity of the signature. ## EXAMPLES Sign the busybox image with the identity 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 +```bash + $ sudo podman image sign --sign-by foo@bar.com --directory /tmp/signatures docker://privateregistry.example.com/foobar - sudo podman image sign --authfile=/tmp/foobar.json --sign-by foo@bar.com --directory /tmp/signatures docker://privateregistry.example.com/foobar + $ sudo podman image sign --authfile=/tmp/foobar.json --sign-by foo@bar.com --directory /tmp/signatures docker://privateregistry.example.com/foobar +``` ## RELATED CONFIGURATION @@ -52,9 +54,11 @@ where to write the signature based on the name of the originating registry or a default storage value unless overridden with the --directory option. For example, consider the following configuration file. +```yaml docker: privateregistry.example.com: sigstore: file:///var/lib/containers/sigstore +``` When signing an image preceded with the registry name 'privateregistry.example.com', the signature is written into sub-directories of