From 753901936ba099790fd5c27ff63bfb0c335fd043 Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Tue, 12 Sep 2017 16:36:41 -0700 Subject: [PATCH] Improve notary setup for DTR (#4603) --- .../configure-your-notary-client.md | 32 ++++++++++++------- 1 file changed, 21 insertions(+), 11 deletions(-) diff --git a/datacenter/dtr/2.3/guides/user/access-dtr/configure-your-notary-client.md b/datacenter/dtr/2.3/guides/user/access-dtr/configure-your-notary-client.md index f1f21482dd..d352c82c00 100644 --- a/datacenter/dtr/2.3/guides/user/access-dtr/configure-your-notary-client.md +++ b/datacenter/dtr/2.3/guides/user/access-dtr/configure-your-notary-client.md @@ -50,7 +50,7 @@ or using a configuration file. Run the Notary command with: ```bash -notary --server https:// --trustDir ~/.docker/trust --tlscacert +notary --server https:// --trustDir ~/.docker/trust --tlscacert --help ``` Here's what the flags mean: @@ -64,13 +64,25 @@ Here's what the flags mean: To avoid having to type all the flags when using the command, you can set an alias: -```none -# Bash -alias notary="notary --server https:// --trustDir ~/.docker/trust --tlscacert " -# PowerShell + +
+
+``` +alias notary="notary --server https:// --trustDir ~/.docker/trust --tlscacert " +``` +
+
+
+``` set-alias notary "notary --server https:// --trustDir ~/.docker/trust --tlscacert " ``` +
+
+
### With a configuration file @@ -90,9 +102,8 @@ the following content: To validate your configuration, try running the `notary list` command on a DTR repository that already has signed images: -```none -# Assumes you've configured notary -notary list +```bash +notary list // ``` The command should print a list of digests for each signed image on the @@ -106,8 +117,7 @@ key of your UCP client bundle. Import the private key in your UCP bundle into the Notary CLI client: -```none -# Assumes you've configured notary +```bash notary key import ``` @@ -116,7 +126,7 @@ password to encrypt it. You can validate what keys Notary knows about by running: -```none +```bash notary key list ```