Support for bundling Chromium unittests into a tarball.

blimp/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 && \

[maniscalco, 2016/06/02 19:15:55]

Let's talk about the Dockerfile OOB.  It would be great if we could find a way
to factor this into a base file or image that's shared by both the engine and
test builds.

[Sriram, 2016/06/02 19:55:05]

+1

[Jess, 2016/06/02 23:02:14]

I intended this Dockerfile as a stub that would need further work. I've hacked
it down to just comments to make that clearer.

Created http://crbug/616945 to track the broader Dockerfile structuring problem.

   apt-get install -yq libdrm2 libfontconfig1 libfreetype6 libgraphite2-3 \
   libharfbuzz0b libnspr4 libnss3 libstdc++6
 
 RUN apt-get update && apt-get install -yq stunnel4 wget
 
-RUN mkdir /engine
+RUN mkdir /out
+RUN mkdir /out/test

[Sriram, 2016/06/02 19:55:05]

could use "mkdir -p" to create all parents as well.

Also any reason to have /out/test instead of say /tests? 

[Jess, 2016/06/02 23:02:14]

Done.

Mostly because I structured this based on how I could get tests running locally.
 My test binaries were looking for data files 2 directory layers under
themselves.

 
 RUN useradd -ms /bin/bash blimp_user
 
 # The glob below expands to all files, but does not add directories
 # recursively.
-ADD * /engine/
-ADD gen/third_party/blimp_fonts /engine/fonts
-RUN mv /engine/chrome_sandbox /engine/chrome-sandbox
-RUN chown -R blimp_user /engine
+ADD * /out/test/
+RUN chown -R blimp_user /out/test
 
 USER blimp_user
-WORKDIR "/engine"
-
-ENTRYPOINT ["/engine/start_engine.sh"]
+WORKDIR "/out/test"