docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update https.md 

editorial crx
This commit is contained in:
L-Hudson 2018-12-07 15:39:01 -05:00 committed by GitHub
parent 9f22f38fa7
commit 43a1cb05a4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
engine/security/https.md
View File

@ -7,10 +7,10 @@ redirect_from:
title: Protect the Docker daemon socket
---
By default, Docker runs via a non-networked Unix socket. It can also
By default, Docker runs through a non-networked UNIX socket. It can also
optionally communicate using an HTTP socket.
If you need Docker to be reachable via the network in a safe manner, you can
If you need Docker to be reachable through the network in a safe manner, you can
enable TLS by specifying the `tlsverify` flag and pointing Docker's
`tlscacert` flag to a trusted CA certificate.
@ -73,7 +73,7 @@ to connect to Docker:
Next, we're going to sign the public key with our CA:
Since TLS connections can be made via IP address as well as DNS name, the IP addresses
Since TLS connections can be made through IP address as well as DNS name, the IP addresses
need to be specified when creating the certificate. For example, to allow connections
using `10.10.10.20` and `127.0.0.1`:
@ -180,7 +180,7 @@ certificates and trusted CA:
## Secure by default
If you want to secure your Docker client connections by default, you can move
the files to the `.docker` directory in your home directory -- and set the
the files to the `.docker` directory in your home directory --- and set the
`DOCKER_HOST` and `DOCKER_TLS_VERIFY` variables as well (instead of passing
`-H=tcp://$HOST:2376` and `--tlsverify` on every call).