Create a set of Dart dockerfiles

base/Dockerfile

+FROM google/debian:wheezy
+
+RUN apt-get -q update; apt-get install --no-install-recommends -y -q wget
+RUN wget -q http://storage.googleapis.com/dart-archive/channels/stable/release/37644/linux_packages/debian_wheezy/dart_1.5.1-1_amd64.deb && dpkg -i dart_1.5.1-1_amd64.deb && rm dart_1.5.1-1_amd64.deb
+
+ENV PATH /usr/lib/dart/bin:$PATH

[kustermann, 2014/07/03 12:39:00]

@proppy: We were discussing whether it makes sense to add "apt-get update &&
apt-get upgrade" here. It doesn't look like the base "google/debian:wheezy"
image does this. But we need to ensure, that if our users re-build & re-deploy
they deploy a healthy system with all security updates in.

[proppy, 2014/07/07 23:47:59]

It's not good practice to run apt-get upgrade in dockerfile, the base debian
image should be kept up to date instead.

[kustermann, 2014/07/08 08:49:08]

We saw you didn't do it for the other runtimes and discussed this a bit:

A linux distribution consists of a large number libraries/applications (even a
small debian). If a security bug gets discovered and fixed in the distribution,
users should get them as quickly as possible. A non-debatable requirement is
that users need to re-build images and re-deploy. Having an "apt-get upgrade" in
here, means users get it as soon as the distribution made a bugfix available. So
once debian has fixed a bug, they can build/deploy within minutes.

Otherwise, it depends how quickly we update the base debian image. Looking at
[0] it seems like "google/debian:wheezy" has not been touched since April --
that's *3 months*!

So:
 - What is the release schedule for the base images?
 - Who is responsible for making the releases (what if he is on vacation ...)?

I think we should take these things seriously.

[0] https://github.com/GoogleCloudPlatform/debian-docker/commits/master