Public | Automated Build

Last pushed: 2 years ago
Short Description
A Centos7 based Ruby v1.9 image for use with OpenShift v3
Full Description

Ruby Docker image

This repository contains the source for building various versions of
the Ruby application as a reproducible Docker image using
The resulting image can be run using Docker.


To build a simple ruby-sample-app application
using standalone S2I and then run the
resulting image with Docker execute:

  • For RHEL based image
    Support for ruby1.9 is being discontinued for rhel7.

  • For CentOS based image

     $ s2i build --context-dir=1.9/test/puma-test-app/ openshift/ruby-19-centos7 ruby-sample-app
     $ docker run -p 8080:8080 ruby-sample-app

Accessing the application:

$ curl

Repository organization

  • <ruby-version>

    • Dockerfile

      CentOS based Dockerfile.

    • s2i/bin/

      This folder contains scripts that are run by S2I:

      • assemble

        Used to install the sources into the location where the application
        will be run and prepare the application for deployment (eg. installing
        modules using bundler, etc.)

      • run

        This script is responsible for running the application by using the
        application web server.

      • usage*

        This script prints the usage of this image.

    • contrib/

      This folder contains a file with commonly used modules.

    • test/

      This folder contains a S2I
      test framework with a simple Rack server.

      • puma-test-app/

        Simple Puma web server used for testing purposes by the S2I test framework.

      • rack-test-app/

        Simple Rack web server used for testing purposes by the S2I test framework.

      • run

        Script that runs the S2I test framework.

Environment variables

To set these environment variables, you can place them as a key value pair into a .sti/environment
file inside your source code repository.


    This variable specifies the environment where the Ruby application will be deployed (unless overwritten) - production, development, test.
    Each level has different behaviors in terms of logging verbosity, error pages, ruby gem installation, etc.

    Note: Application assets will be compiled only if the RACK_ENV is set to production


    This variable set to true indicates that the asset compilation process will be skipped. Since this only takes place
    when the application is run in the production environment, it should only be used when assets are already compiled.

Hot deploy

In order to dynamically pick up changes made in your application source code, you need to make following steps:

  • For Ruby on Rails applications

    Run the built Rails image with the RAILS_ENV=development environment variable passed to the Docker -e run flag:

     $ docker run -e RAILS_ENV=development -p 8080:8080 rails-app
  • For other types of Ruby applications (Sinatra, Padrino, etc.)

    Your application needs to be built with one of gems that reloads the server every time changes in source code are done inside the running container. Those gems are:

    • Shotgun
    • Rerun
    • Rack-livereload

      Please note that in order to be able to run your application in development mode, you need to modify the S2I run script, so the web server is launched by the chosen gem, which checks for changes in the source code.

      After you built your application image with your version of S2I run script, run the image with the RACK_ENV=development environment variable passed to the Docker -e run flag:

      $ docker run -e RACK_ENV=development -p 8080:8080 sinatra-app

To change your source code in running container, use Docker's exec command:

docker exec -it <CONTAINER_ID> /bin/bash

After you Docker exec into the running container, your current
directory is set to /opt/app-root/src, where the source code is located.

Docker Pull Command
Source Repository