Convert the long RUN into many small, caching RUNs

[bflad]

No description provided.

[justincampbell]

@bflad The intent was to create as small of a download as possible for users of this base image. Things such as the ruby-install, the Ruby source, and install dependencies are of little use for a production deployment, and the cache would be mostly invalidated with each new version bump.

I don't have exact numbers right now, but I'm pretty sure the difference was a few hundred megabytes when we tested it.

Thoughts? I'm a bit of a Docker newbie, so let me know if there are any cons to this style, other than readability.

[bflad]

Ha when Mike and I were writing this last night we thought the same thing.
Seems like the docker trusted builds should allow you to remove the
intermediate layers as an option. I haven't looked but is there an
issue/discussion about that feature anywhere?

Brian Flad
Sent from mobile
On Feb 26, 2014 7:59 AM, "Justin Campbell" notifications@github.com wrote:

@bflad https://github.com/bflad The intent was to create as small of a
download as possible for users of this base image. Things such as the
ruby-install, the Ruby source, and install dependencies are of little use
for a production deployment, and the cache would be mostly invalidated with
each new version bump.

I don't have exact numbers right now, but I'm pretty sure the difference
was a few hundred megabytes when we tested it.

Thoughts? I'm a bit of a Docker newbie, so let me know if there are any
cons to this style, other than readability.

Reply to this email directly or view it on GitHubhttps://github.com//pull/2#issuecomment-36122046
.

[justincampbell]

moby/moby#332

and also semi-related moby/moby#4232

[justincampbell]

I think #3 solves this