reweave/weave
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cosmetic: tweak link

Browse Source
This commit is contained in:
Matthias Radestock committed 2016-03-28 16:25:12 +01:00
1 parent db9139a0cd
commit 2948deb210
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
site/using-weave/service-management.md
+1 -1
View File
@@ -50,7 +50,7 @@ Using the netcat service example described in
An additional caveat is that `$HOST3` can only be reached from `$HOST1`, which is not accessible via `$HOST2`. Nonetheless, you still need to make the `$HOST3` service available to an application that is running in a container on `$HOST2`.
To satisfy this scenario, first expose the [application network to the host](/site/using-weave/host-network-integration.md) by running the following on `$HOST1`:
To satisfy this scenario, first [expose the application network to the host](/site/using-weave/host-network-integration.md) by running the following on `$HOST1`:
host1$ weave expose -h host1.weave.local
10.2.1.3