Set up an stunnel endpoint for the engine.

blimp/engine/Dockerfile

 FROM ubuntu:trusty
 
 # Run the command below to update the lib list.
 # ldd ./blimp_engine_app | grep usr/lib | awk '{print $3}' | xargs -n1 \
 #   dpkg-query -S | awk -F: '{print $1}' | sort | uniq
 RUN apt-get update && \
   apt-get install -yq libdrm2 libfontconfig1 libfreetype6 libgraphite2-3 \
   libharfbuzz0b libnspr4 libnss3 libstdc++6
 
+RUN apt-get update && apt-get install -yq stunnel4

[Kevin M, 2016/01/28 21:54:12]

This "update" looks redundant?

Also, can stunnel4 be rolled in with the other args to apt-get install?

[marcinjb, 2016/01/28 22:15:38]

I'd like to keep it separate as one apt-get is the runtime dependencies of the
engine app, the other is our stunnel wrapper.  

The extra update has been excised.

+
 RUN mkdir /engine
 
 RUN useradd -ms /bin/bash blimp_user
 
 ADD * /engine/
 RUN mv /engine/chrome_sandbox /engine/chrome-sandbox
 RUN chown -R blimp_user /engine
 
 USER blimp_user
 WORKDIR "/engine"
 
-ENTRYPOINT ["/engine/blimp_engine_app", \
-                "--disable-gpu", \
-                "--use-remote-compositing", \
-                # Retains display items for serialization on the engine.
-                "--disable-cached-picture-raster", \
-                "--blimp-client-token-path=/engine/data/client_token"]
+ENTRYPOINT ["/engine/start_engine.sh"]
+