From ef453f7118d704319768d8d9c0cfe79e2d521afa Mon Sep 17 00:00:00 2001 From: moxiegirl Date: Thu, 13 Aug 2015 06:42:26 -0700 Subject: [PATCH] Fixing bad formatting reported by David via email Fixed and tested Signed-off-by: Mary Anthony --- docs/security/trust/trust_automation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/security/trust/trust_automation.md b/docs/security/trust/trust_automation.md index 0808d8cef2..08caa84956 100644 --- a/docs/security/trust/trust_automation.md +++ b/docs/security/trust/trust_automation.md @@ -32,7 +32,7 @@ $ export DOCKER_CONTENT_TRUST_TAGGING_PASSPHRASE="l7pEQcTKJjUHm6Lpe4" Then, when pushing a new tag the Docker client does not request these values but signs automatically: -``bash +```bash $ docker push docker/trusttest:latest The push refers to a repository [docker.io/docker/trusttest] (len: 1) a9539b34a6ab: Image already exists @@ -45,7 +45,7 @@ Signing and pushing trust metadata You can also build with content trust. Before running the `docker build` command, you should set the environment variable `DOCKER_CONTENT_TRUST` either manually or in in a scripted fashion. Consider the simple Dockerfile below. -```Dockerfilea +```Dockerfile FROM docker/trusttest:latest RUN echo ```