Set up an stunnel endpoint for the engine.

blimp/docs/container.md

Index: blimp/docs/container.md
diff --git a/blimp/docs/container.md b/blimp/docs/container.md
index 36a5ceee32266b196e117e820eac244a690114de..7cf9eecdfb9edcfd88c02790d0990d23734dfffb 100644
--- a/blimp/docs/container.md
+++ b/blimp/docs/container.md
@@ -87,3 +87,11 @@ docker run -v /path/to/srcdir:/path/to/docker/destdir blimp_engine
 
 NB: The permissions of the directory and the files outside of the Docker
 container will be carried over into the container.
+
+### Mapping Ports for the Docker Container

[maniscalco, 2016/01/27 17:02:10]

I think it might be time to revamp some of the docs that explain how to run the
engine.   As of this CL, in order to run the engine in a container we need both
-v and -p right?  How about we rewrite/combine this section with the two
sections above into one section and reconcile with the running.md doc:
https://code.google.com/p/chromium/codesearch#chromium/src/blimp/docs/running.md

+
+If you need to open a port for the Docker container in order to communicate:
+
+```bash
+docker run -p localport:dockerport blimp_engine
+```