TrueCloudLab/distribution
13
0
Fork 3
Code Issues 2 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Update deploying.md

Browse source
This commit is contained in:
Wang Jie 2017-10-20 09:33:36 +08:00 committed by Misty Stanley-Jones
parent e95522ec45
commit b5975461f0
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/deploying.md
View file

@ -45,7 +45,7 @@ as `my-ubuntu`, then pushes it to the local registry. Finally, the
``` ```
2. Tag the image as `localhost:5000/my-ubuntu`. This creates an additional tag 2. Tag the image as `localhost:5000/my-ubuntu`. This creates an additional tag
for the existing image.When the first part of the tag is a hostname and for the existing image. When the first part of the tag is a hostname and
port, Docker interprets this as the location of a registry, when pushing. port, Docker interprets this as the location of a registry, when pushing.
```bash ```bash
@ -333,7 +333,7 @@ $ docker service create \
You can access the service on port 80 of any swarm node. Docker sends the You can access the service on port 80 of any swarm node. Docker sends the
requests to the node which is running the service. requests to the node which is running the service.
## Load Balancing Considerations ## Load balancing considerations
One may want to use a load balancer to distribute load, terminate TLS or One may want to use a load balancer to distribute load, terminate TLS or
provide high availability. While a full load balancing setup is outside the provide high availability. While a full load balancing setup is outside the
@ -447,7 +447,7 @@ secrets.
Provide the username and password from the first step. Provide the username and password from the first step.
Test that you can now pull an image from the registry or push an image to Test that you can now pull an image from the registry or push an image to
the registry.. the registry.
> **X509 errors**: X509 errors usually indicate that you are attempting to use > **X509 errors**: X509 errors usually indicate that you are attempting to use
> a self-signed certificate without configuring the Docker daemon correctly. > a self-signed certificate without configuring the Docker daemon correctly.