Chapter 7. Application Images

The rhscl/nodejs-6-rhel7 image provides a Node.js 6 platform for building and running applications. The rhscl/nodejs-4-rhel7 image provides a Node.js 4 platform.

To pull the rhscl/nodejs-6-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/nodejs-6-rhel7

To pull the rhscl/nodejs-4-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/nodejs-4-rhel7

No further configuration is required.

The rhscl/perl-524-rhel7 image provides a Perl 5.24 platform for building and running applications, the rhscl/perl-520-rhel7 image provides a Perl 5.20 platform. Apache httpd 2.4 with mod_perl for deploying Perl web applications is preinstalled. The images also supports deploying Perl Web Server Gateway Interface (PSGI) applications.

To pull the rhscl/perl-524-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/perl-524-rhel7

To pull the rhscl/perl-520-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/perl-520-rhel7

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

To install additional Perl modules from the Comprehensive Perl Archive Network (CPAN), create a cpanfile in the root directory of your application sources. The file must conform to the cpanfile format as defined in Module-CPANFile CPAN distribution. For detailed information about the cpanfile format, refer to the cpanfile documentation.

To modify the Apache httpd behavior, drop the .htaccess file in the application sources tree where appropriate. For details about .htaccess, see the Apache HTTP Server Tutorial.

The rhscl/php-70-rhel7 image provides a PHP 7.0 platform for building and running applications, the rhscl/php-56-rhel7 image provides a PHP 5.6 platform.

To pull the rhscl/php-70-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/php-70-rhel7

To pull the rhscl/php-56-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/php-56-rhel7

To set environment variables, place them as a key-value pair into a .s2i/environment file inside your source code repository.

The following environment variables set their equivalent property value in the php.ini file:

The following environment variable sets its equivalent property value in the opcache.ini file:

You can also override the entire directory used to load the PHP configuration by setting:

In case the DocumentRoot of the application is nested within the source directory /opt/app-root/src, users can provide their own .htaccess file. This allows the overriding of Apache’s behavior and specifies how application requests should be handled. The .htaccess file needs to be located at the root of the application source. For details about .htaccess, see the Apache HTTP Server Tutorial.

The rhscl/python-35-rhel7 image provides a Python 3.5 platform for building and running applications. The rhscl/python-34-rhel7 image includes a Python 3.4 platform, and the rhscl/python-27-rhel7 image provides a Python 2.7 platform.

To pull the rhscl/python-35-rhel7 image, run the following command as root:

# podman pull registry.access.redhat.com/rhscl/python-35-rhel7

To pull the rhscl/python-34-rhel7 image, run the following command as root:

# podman pull registry.access.redhat.com/rhscl/python-34-rhel7

To pull the rhscl/python-27-rhel7 image, run the following command as root:

# podman pull registry.access.redhat.com/rhscl/python-27-rhel7

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

The rhscl/ruby-24-rhel7 image provides a Ruby 2.4 platform for building and running applications; Node.js 6 is preinstalled for assets compilation.

The rhscl/ruby-23-rhel7 image provides a Ruby 2.3 platform for building and running applications; Node.js 4 is preinstalled for assets compilation.

The rhscl/ruby-22-rhel7 image provides a Ruby 2.2 platform; Node.js 0.10 is preinstalled for assets compilation.

To pull the rhscl/ruby-24-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/ruby-24-rhel7

To pull the rhscl/ruby-23-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/ruby-23-rhel7

To pull the rhscl/ruby-22-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/ruby-22-rhel7

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

For S2I scripts to work, you need to include the puma or rack gem in the application’s Gemfile.

The rhscl/ror-50-rhel7 provides a Ruby on Rails 5.0 platform for building and running applications and it contains Ruby 2.4, Ruby on Rails 5.0, and Node.js 6 preinstalled.

The rhscl/ror-42-rhel7 provides a Ruby on Rails 4.2 platform for building and running applications and it contains Ruby 2.3, Ruby on Rails 4.2, and Node.js 4 preinstalled.

The rhscl/ror-41-rhel7 provides a Ruby on Rails 4.1 platform and it contains Ruby 2.2, Ruby on Rails 4.1, and Node.js 0.10 preinstalled.

To pull the rhscl/ror-50-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/ror-50-rhel7

To pull the rhscl/ror-42-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/ror-42-rhel7

To pull the rhscl/ror-41-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/ror-41-rhel7

No further configuration is required.

The rhscl/ror-50-rhel7 image contains and enables the rh-ruby24, rh-ror50, and rh-nodejs6 Software Collections. The rhscl/ror-42-rhel7 image contains and enables the rh-ruby23, rh-ror42, and rh-nodejs4 Software Collections. The rhscl/ror-41-rhel7 image contains and enables the rh-ruby22, rh-ror41, and nodejs010 Software Collections.

For automatic S2I builds, use the Ruby container.

The rhscl/passenger-40-rhel7 image provides a Phusion Passenger 4.0 application server configured with Apache httpd web server. It also provides a Ruby 2.2 platform for building and running applications. Node.js 0.10 is preinstalled for assets compilation.

To pull the rhscl/passenger-40-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/passenger-40-rhel7

No further configuration is required; this image contains and enables the rh-ruby22, rh-ror41, nodejs010, rh-passenger40, and httpd24 Software Collections. It is especially designed to support automatic S2I builds.

The rhscl/thermostat-16-agent-rhel7 image provides a thermostat agent suitable for monitoring Java applications in containers.

The rhscl/thermostat-16-agent-rhel7 and rhscl/thermostat-1-agent-rhel7 images are no longer supported.

To pull the rhscl/thermostat-16-agent-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/thermostat-16-agent-rhel7

The image is intended to be used as a base image for builder and runtime images in your Dockerfile using:

FROM rhscl/thermostat-16-agent-rhel7

See this example of a Dockerfile, which will have the Thermostat agent pre-installed.

Once the rhscl/thermostat-16-agent-rhel7 image has been introduced into the image hierarchy, the Thermostat agent can be started by setting the three required Thermostat environment variables. For example, an image called rhscl/thermostat-test uses rhscl/thermostat-16-agent-rhel7 as its base image and runs Java app foo on deployment. A Thermostat agent can be started together with foo by setting the following environment variables:

The rhscl/thermostat-16-storage-rhel7 image can be used to set up a storage endpoint for the agent to connect to.

The image recognizes the following environment variables that you can set during initialization by passing -e VAR=VALUE to the docker run command:

The rhscl/thermostat-16-storage-rhel7 contains a Thermostat 1.6 storage, which provides a web endpoint for storing and retrieving data. This image is based on the rh-thermostat16 Software Collection.

The rhscl/thermostat-16-storage-rhel7 image is no longer supported.

To pull the rhscl/thermostat-16-storage-rhel7 image, run the following command as root:

# docker pull registry.access.redhat.com/rhscl/thermostat-16-storage-rhel7

To run Thermostat storage connected to some other MongoDB backend (for example, provided by another container), you need to provide the MongoDB URL, mongo user name and password, and agent and client user names and passwords. Run the following command:

# docker run -d \
  -e MONGO_URL=mongodb://172.17.0.1:27017 \
  -e MONGO_USERNAME=<mongouser> \
  -e MONGO_PASSWORD=<mongopass> \
  -e THERMOSTAT_AGENT_USERNAMES=<agentuser1,agentuser2> \
  -e THERMOSTAT_AGENT_PASSWORDS=<agentpass1,agentpass2> \
  -e THERMOSTAT_CLIENT_USERNAMES=<clientuser1,clientuser2> \
  -e THERMOSTAT_CLIENT_PASSWORDS=<clientpass1,clientpass2> \
  --name thermostat16-storage \
  rhscl/thermostat-16-storage-rhel7

This will run a container with the HTTP layer connected to the MongoDB URL using the provided mongo user name and password. The container can be accessed at http://ip-address:8080/thermostat/storage with the appropriate client or agent credentials that you specified with the environment variables. To find the IP address, run the following command:

# docker inspect --format '\{\{ .NetworkSettings.IPAddress }}' thermostat16-storage

The command from the example above creates the following agent users:

Either one of them, or both, can be used for Thermostat agent connections.

In addition, the following client users will be usable:

Either one of them, or both, can be used for Thermostat client connections.

The rhscl/thermostat-16-storage-rhel7 image recognizes the following environment variables that you can set during initialization by passing -e VAR=VALUE to the docker run command: