Update use-domain-names-to-access-services.md (#2943)

* Update use-domain-names-to-access-services.md

Fixed https://github.com/docker/docker.github.io/issues/2580

* Update use-domain-names-to-access-services.md
This commit is contained in:
Prashant 2017-04-21 01:59:49 +05:30 committed by Misty Stanley-Jones
parent 553db19401
commit d4047a2cb5
1 changed files with 11 additions and 2 deletions

View File

@ -95,8 +95,7 @@ to your services.
The HTTP routing mesh can route to a service, as long as that service:
* Is attached to a network that has the `com.docker.ucp.mesh.http` label. You
can use the default `ucp-hrm` network or create your own
* Is attached to a network that has the `com.docker.ucp.mesh.http` label. You can use the default ucp-hrm network or create your own.
* Publishes the ports that you want to route to
* Has one or more labels with the prefix `com.docker.ucp.mesh.http`, specifying
the ports to route to
@ -179,3 +178,13 @@ enabling the HTTP routing mesh:
The HTTP routing mesh will route to all services in these networks, but services
on different networks can't communicate directly.
When using a UCP client bundle for an admin user, or a user with administrator privileges,
you can create an overlay network that contains the `com.docker.mesh.http` label by running the following command.
```none
docker network create -d overlay --label com.docker.ucp.mesh.http=true new-hrm-network
```
If you're creating a a new HRM network you need to disable the HRM service first, or disable
and enable the HRM service after you create the network else HRM will not be available on new network.