Skip to content

Commit d82e8c9

Browse files
abjinugujoaofnfernandes
authored andcommitted
HRM and Window Servers (docker#5962)
* HRM and Window Servers Note:- Windows Server doesn't support Swarm Mode Routing Mesh yet (not considering Windows Server version 1709 which will be out soon). This means the hrm service is exposed only through the manager node's ip (since Windows Server cannot be a manager node). Therefore the DNS entry for the host name ('wordpress.example.org' in this example) should be mapped to the manager node and not to any of the Windows worker nodes. * HRM with Windows Server HRM with Windows Server
1 parent 374d240 commit d82e8c9

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

datacenter/ucp/2.2/guides/user/services/use-domain-names-to-access-services.md

+9
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,15 @@ Now that WordPress is deployed, add a new DNS entry that maps
7070
When testing locally, you can also change your `/etc/hosts` file to
7171
create this mapping, instead of using a DNS service.
7272

73+
> #### HRM with Windows Server:
74+
> Windows Server doesn't support Swarm Mode Routing Mesh yet
75+
> (*not considering Windows Server version 1709 which will be out soon*).
76+
> This means the hrm service is exposed only through the manager node's ip
77+
> (*since Windows Server cannot be a manager node*).
78+
> DNS entry for the host name('wordpress.example.org' in this example) should
79+
> therefore be mapped to manager nodes and not to any of the Windows worker
80+
> nodes.
81+
7382
Once this is done, you can access the wordpress service from your browser.
7483

7584
![](../../images/use-domain-names-7.png){: .with-border}

0 commit comments

Comments
 (0)