refactor: more logical question ordering
This commit is contained in:
1 parent
de1304d424
commit
019a065d03
1 file changed
+5
-5
+5
-5
@@ -12,11 +12,6 @@ You can use `weave ps <container>` to see the allocated address of a container o
|
||||
See [Troubleshooting Weave - List attached containers](/site/troubleshooting.md#list-attached-containers).
|
||||
|
||||
|
||||
**Q: How do I expose one of my containers to the outside world?**
|
||||
|
||||
Exposing a container to the outside world is described in [Exposing Services to the Outside](/site/using-weave/service-export.md).
|
||||
|
||||
|
||||
**Q: My dockerized app needs to check the request of an application that uses a static IP. Is it possible to manually change the IP of a container?**
|
||||
|
||||
|
||||
@@ -25,6 +20,11 @@ You can manually change the IP of a container using [Classless Inter-Domain Rout
|
||||
For more information, refer to [Manually Specifying the IP Address of a Container](/site/using-weave/manual-ip-address.md).
|
||||
|
||||
|
||||
**Q: How do I expose one of my containers to the outside world?**
|
||||
|
||||
Exposing a container to the outside world is described in [Exposing Services to the Outside](/site/using-weave/service-export.md).
|
||||
|
||||
|
||||
**Q: Can I connect my existing 'legacy' network with a Weave container network?**
|
||||
|
||||
Yes you can.
|
||||
|
||||
Reference in new issue
Block a user