This is a cache of https://docs.openshift.com/container-platform/4.16/openshift_images/using_images/using-s21-images.html. It is a snapshot of the page at 2024-11-22T09:42:02.092+0000.
Source-to-image - Using images | Images | OpenShift Container Platform 4.16
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Source-to-image

You can use the Red Hat Software Collections images as a foundation for applications that rely on specific runtime environments such as Node.js, Perl, or Python. You can use the Red Hat Java Source-to-Image for OpenShift documentation as a reference for runtime environments that use Java. Special versions of some of these runtime base images are referred to as Source-to-Image (s2i) images. With s2i images, you can insert your code into a base image environment that is ready to run that code.

s2i images include:

  • .NET

  • Java

  • Go

  • Node.js

  • Perl

  • PHP

  • Python

  • Ruby

s2i images are available for you to use directly from the OpenShift Container Platform web console by following procedure:

  1. Log in to the OpenShift Container Platform web console using your login credentials. The default view for the OpenShift Container Platform web console is the Administrator perspective.

  2. Use the perspective switcher to switch to the Developer perspective.

  3. In the +Add view, use the Project drop-down list to select an existing project or create a new project.

  4. Click All services in the Developer Catalog tile.

  5. Click Builder Images under Type to see the available s2i images.

s2i images are also available though the Cluster Samples Operator.

Source-to-image build process overview

Source-to-image (s2i) produces ready-to-run images by injecting source code into a container that prepares that source code to be run. It performs the following steps:

  1. Runs the FROM <builder image> command

  2. Copies the source code to a defined location in the builder image

  3. Runs the assemble script in the builder image

  4. Sets the run script in the builder image as the default command

Buildah then creates the container image.

Additional resources