centurylink/ruby-base repository overview

Debian-based Docker image containing stable versions of Ruby, RubyGems and Bundler.

The version of Ruby in this image has been compiled from source and every effort has been made to keep the image size as small as possible

This repository provides different images for different versions of Ruby. The list below shows available Ruby versions along with the image size and all of the image tags which may be referenced:

• 2.2.2, 2.2, 2, latest (349MB, Dockerfile⁠)
• 2.2.0 (358MB, Dockerfile⁠)
• 2.1.6, 2.1 (348MB, Dockerfile⁠)
• 2.1.5 (348MB, Dockerfile⁠)
• 2.1.3 (346MB, Dockerfile⁠)
• 2.1.2 (346MB, Dockerfile⁠)
• 2.0.0-p598, 2.0.0, 2.0 (350MB, Dockerfile⁠)
• 2.0.0-p576 (335MB, Dockerfile⁠)
• 1.9.3-p551, 1.9.3, 1.9, 1 (318MB, Dockerfile⁠)
• 1.9.3-p547 (304MB, Dockerfile⁠)

The Dockerfiles for all of the images can be found in the centurylinklabs/ruby-base-image⁠ repo on GitHub.

This image can be used as the base for your Ruby application by referencing this image in the FROM line of your Dockerfile:

FROM centurylink/ruby-base:2.1.2

It can also be used as an interactive Ruby environment by simply running the image with the -it flags:

docker run -it centurylink/ruby-base:2.1.2
irb(main):001:0> RUBY_VERSION
=> "2.1.2"
irb(main):002:0> 

⁠Why doesn't this repo use Automated Builds?

The Docker Hub's Automated Builds⁠ feature is a little clunky when you have a repo like this with many images and lots of different tags for those images. It is possible to set-up, but any time you want to add a new tag you have to trigger a new build for all the tags. We found it was more efficient to simply build our images locally and push them up to the Hub. Note that none of Docker's "official" repos use the automated build feature -- we suspect it's for the same reason.