alexvanin/distribution
1
0
Fork 0
forked from TrueCloudLab/distribution
Code Pull requests Activity

Docs: replace emoji with regular warning

Browse source 
The docs don't render emoji, so replaced the `⚠️` with
a `**Warning**:` to keep the formatting consisten with
`**Note**:` used in other parts of the docs.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Sebastiaan van Stijn 2015-10-22 15:21:02 -07:00
parent a266f99418
commit bf6ca6cb53
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/deploying.md
View file

@ -148,7 +148,7 @@ Except for registries running on secure local networks, registries should always
The simplest way to achieve access restriction is through basic authentication (this is very similar to other web servers' basic authentication mechanism). The simplest way to achieve access restriction is through basic authentication (this is very similar to other web servers' basic authentication mechanism).
:warning: You **cannot** use authentication with an insecure registry. You have to [configure TLS first](#running-a-domain-registry) for this to work. > **Warning**: You **cannot** use authentication with an insecure registry. You have to [configure TLS first](#running-a-domain-registry) for this to work.
First create a password file with one entry for the user "testuser", with password "testpassword": First create a password file with one entry for the user "testuser", with password "testpassword":
@ -213,7 +213,7 @@ registry:
- /path/auth:/auth - /path/auth:/auth
``` ```
:warning: replace `/path` by whatever directory that holds your `certs` and `auth` folder from above. > **Warning**: replace `/path` by whatever directory that holds your `certs` and `auth` folder from above.
You can then start your registry with a simple You can then start your registry with a simple

4
docs/insecure.md
View file

@ -14,7 +14,7 @@ You have to understand the downsides in doing so, and the extra burden in config
## Deploying a plain HTTP registry ## Deploying a plain HTTP registry
> :warning: it's not possible to use an insecure registry with basic authentication > **Warning**: it's not possible to use an insecure registry with basic authentication
This basically tells Docker to entirely disregard security for your registry. This basically tells Docker to entirely disregard security for your registry.
@ -32,7 +32,7 @@ This basically tells Docker to entirely disregard security for your registry.
## Using self-signed certificates ## Using self-signed certificates
> :warning: using this along with basic authentication requires to **also** trust the certificate into the OS cert store for some versions of docker (see below) > **Warning**: using this along with basic authentication requires to **also** trust the certificate into the OS cert store for some versions of docker (see below)
Generate your own certificate: Generate your own certificate: