docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #15560 from docker/patch-bad-formatting 

Fixing bad formatting reported by David via email
This commit is contained in:
Sebastiaan van Stijn 2015-08-13 20:26:05 +02:00
parent 355f640d4d ef453f7118
commit 599b76000d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/security/trust/trust_automation.md
View File

@ -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: Then, when pushing a new tag the Docker client does not request these values but signs automatically:
``bash ```bash
$ docker push docker/trusttest:latest $ docker push docker/trusttest:latest
The push refers to a repository [docker.io/docker/trusttest] (len: 1) The push refers to a repository [docker.io/docker/trusttest] (len: 1)
a9539b34a6ab: Image already exists 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. 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 FROM docker/trusttest:latest
RUN echo RUN echo
``` ```