clearlinux/docker
2
0
Fork 0
mirror of https://github.com/clearlinux/docker.git synced 2026-09-04 12:41:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing bad formatting reported by David via email

Browse Source 
Fixed and tested

Signed-off-by: Mary Anthony <mary@docker.com>
(cherry picked from commit ef453f7118)
This commit is contained in:
moxiegirl
2015-08-19 09:52:40 -07:00
committed by Mary Anthony
parent d3fe81f9ba
commit e1eee1290d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/security/trust/trust_automation.md
+2 -2
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:
``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
```