Work out the kinks for running Strider on Carina

[smashwilson]

Strider's eventual home will be on a Carina cluster (along with the rest of the cluster), so I want to be certain it can run there. One it can run on Carina, it will certainly be able to run on our own CoreOS cluster.

Current problems:

• [x] Strider needs to run as root so that it can launch other Docker containers through the Docker socket.
• [x] git and perl are needed by the git provider.

  Control repository builds

• [x] npm attempts to use root-owned paths for its cache.

  >> Waiting for preparer container completion. { containerId: '7e3b638c1f2f18788edb8e8b2da5b6259031306f4825be3a7e363c2e19bbb924' }
  npm ERR! Linux 3.18.21-1-rackos
  npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
  npm ERR! node v0.12.9
  npm ERR! npm  v2.14.9
  npm ERR! path /var/control-repo/.tmp
  npm ERR! code EACCES
  npm ERR! errno -13

• [x] Asset preparer runs with admin API key.

  Content repository builds

• [x] Build data directories are owned by root.

  / # cd workspace/
  /workspace # ls -l
  total 2
  drwxr-xr-x    3 1000     1000          1024 Jan 29 20:45 cache
  drwxr-xr-x    3 1000     1000          1024 Jan 29 20:59 data
  /workspace # cd data/
  /workspace/data # ls -l
  total 1
  drwxr-xr-x    7 root     root          1024 Jan 29 20:59 deconst-deconst-docs-56abd2b59d07e50100c91757

[smashwilson]

Control repository and content repository builds are working on Carina. :raised_hands:

[rgbkrk]

Oooh nice.