kotovalexarian-likes-github
/
moby--moby
mirror of https://github.com/moby/moby.git
1
0
Fork 0
Code Releases Activity

use the Docker Hub as the product name 

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
This commit is contained in:
Sven Dowideit 2015-08-18 21:13:57 +10:00
parent 66112a7ae5
commit 30cde97e5c
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -33,7 +33,7 @@ Finally, you'll need to have `git` installed on your local system or VM.
## What is in the sandbox?
If you are just using trust out-of-the-box you only need your Docker Engine
client and access to Docker's own public hub. The sandbox mimics a
client and access to the Docker hub. The sandbox mimics a
production trust environment, and requires these additional components:
| Container | Description |
@ -45,7 +45,7 @@ production trust environment, and requires these additional components:
| MySQL | The database where all of the trust information will be stored |
The sandbox uses the Docker daemon on your local system. Within the `notarysandbox`
you interact with a local registry rather than the public Docker Hub. This means
you interact with a local registry rather than the Docker Hub. This means
your everyday image repositories are not used. They are protected while you play.
When you play in the sandbox, you'll also create root and tagging keys. The

2
docs/userguide/image_management.md
View File

@ -50,4 +50,4 @@ publisher of all the data received from a registry over any channel.
[Content trust](/security/trust) is currently only available for users of the
public Docker Hub. It is currently not available for the Docker Trusted Registry
or for private registries.
or for private registries.