upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor synced 2025-04-12 22:50:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add notary remove part in notary_guide.md

Browse Source 
Signed-off-by: danfengliu <danfengl@vmware.com>
This commit is contained in:
danfengliu 2019-12-26 18:08:53 +08:00
parent f14a16bedb
commit 0afb52b510
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/1.10/working-with-projects/project-configuration/implementing-content-trust.md
View File

@ -19,10 +19,16 @@ The root key is generated at: `/root/.docker/trust/private/root_keys`
You will also be asked to enter a new passphrase for the image. This is generated at `/root/.docker/trust/private/tuf_keys/[registry name] /[imagepath]`.
If you are using a self-signed cert, make sure to copy the CA cert into `/etc/docker/certs.d/10.117.169.182` and `$HOME/.docker/tls/10.117.169.182:4443/`. When an image is signed, it is indicated in the Web UI.
When an image is signed, it has a tick shown in UI; otherwise, a cross sign(X) is displayed instead.
If you want to remove a tag signature from harbor, you can use 'notary remove' command:
```sh
notary remove -p 10.117.169.182/libary/alpine latest
```
{{< note >}}
Replace "10.117.169.182" with the IP address or domain name of your Harbor node. In order to use content trust, HTTPS must be enabled in Harbor.
{{< /note >}}
When an image is signed, it has a tick shown in UI; otherwise, a cross sign(X) is displayed instead.
![browse project](../../../img/content-trust.png)