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

edits from awh

Browse Source
This commit is contained in:
Anita Buehrle committed 2016-03-08 12:14:27 -06:00
1 parent e2c8dba981
commit be2dfda78e
3 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

site/using-weave/service-management.md
+1 -1
View File
@@ -48,7 +48,7 @@ Weave hosts, regardless of where the actual application containers are located.
Using the netcat service example described in
[Deploying Applications](/site/using-weave/deploying-applications.md), and expanding upon it, you now decide to add a third containerized netcat service. This additional netcat service runs on `$HOST3`, and listens on port 2211, but it is not on the Weave network.
An additional caveat is that `$HOST3` can only be reached from `$HOST1`, which is not accessible via `$HOST2`. Nonetheless, you still need to make a `$HOST3` service available to an application that is running in a container on `$HOST2`.
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`: