Origin S2I NodeJS
This repository contains sources for an s2i builder image, based on CentOS7 and Node.js releases from nodejs.org.
If you are interested in developing against SCL-based Node.js releases, try sti-nodejs.
For more information about using these images with OpenShift, please see the official OpenShift Documentation.
Node.js versions currently provided:
7.10.0: (7.10.0, 7, 7.10, current, latest)
6.10.3: (6.10.3, 6, 6.10, lts, Boron)
5.12.0: (5.12.0, 5, 5.12)
4.8.3: (4.8.3, 4, 4.8, lts, Argon)
Operating systems currently provided are: centos7, fedora
OpenShift allows you to quickly start a build using the web console, or the CLI.
oc command-line tool can be used to start a build, layering your desired nodejs
REPO_URL sources into a centos7 image with your selected
RELEASE of Node.js via the following command format:
oc new-app bucharestgold/centos7-s2i-nodejs:RELEASE~REPO_URL
For example, you can run a build (including
npm install steps), using
s2i-nodejs example repo, and the
current relase of Node.js with:
oc new-app bucharestgold/centos7-s2i-nodejs:current~https://github.com/bucharest-gold/s2i-nodejs
Or, to run the latest
oc new-app bucharestgold/centos7-s2i-nodejs:lts~https://github.com/bucharest-gold/s2i-nodejs
You can try using any of the available tagged Node.js releases, and your own repo sources - as long as your application source will init correctly with
npm start, and listen on port 8080.
Application developers can use the following environment variables to configure the runtime behavior of this image:
|NPM_RUN||Select an alternate / custom runtime mode, defined in your
|NPM_MIRROR||Sets the npm registry URL|
|NODE_ENV||Node.js runtime mode (default: "production")|
|HTTP_PROXY||use an npm proxy during assembly|
|HTTPS_PROXY||use an npm proxy during assembly|
One way to define a set of environment variables is to include them as key value pairs in your repo's
Using Docker's exec
To change your source code in a 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 for your application is located.
Using OpenShift's rsync
If you have deployed the container to OpenShift, you can use oc rsync to copy local files to a remote container running in an OpenShift pod.
This example will produce a new docker image named
s2i build https://github.com/bucharest-gold/s2i-nodejs bucharestgold/centos7-s2i-nodejs:current webapp
There are several ways to make this base image and the full list of tagged Node.js releases available to users during OpenShift's web-based "Add to Project" workflow.
For OpenShift Online Next Gen Developer Preview
Those without admin privileges can install the latest Node.js releases within their project context with:
oc create -f https://raw.githubusercontent.com/bucharest-gold/origin-s2i-nodejs/master/image-streams.json
To ensure that each of the latest Node.js release tags are available and displayed correctly in the web UI, try upgrading / reinstalling the image stream:
oc delete is/centos7-s2i-nodejs ; oc create -f https://raw.githubusercontent.com/bucharest-gold/origin-s2i-nodejs/master/image-streams.json
If you've (automatically) imported this image using the
oc new-app example command, then you may need to clear the auto-imported image stream reference and re-install it.
Administrators can make these Node.js releases available globally (visible in all projects, by all users) by adding them to the
oc create -n openshift -f https://raw.githubusercontent.com/bucharest-gold/origin-s2i-nodejs/master/image-streams.json
To replace the default SCL-packaged
openshift/nodejs image (admin access required), run:
oc delete is/nodejs -n openshift ; oc create -n openshift -f https://raw.githubusercontent.com/bucharest-gold/origin-s2i-nodejs/master/centos7-s2i-nodejs.json
Building your own Builder images
Clone a copy of this repo to fetch the build sources:
git clone https://github.com/bucharest-gold/origin-s2i-nodejs.git cd origin-s2i-nodejs
To build your own S2I Node.js builder images from scratch, run:
You can also build a specific release, or try building the alternate
ONBUILD version of this base:
ONBUILD=true make VERSION=6.3.1
ONBUILD base images are available at https://hub.docker.com/r/bucharestgold/centos7-nodejs
This repository also provides a S2I test framework, which launches tests to check functionality of a simple Node.js application built on top of the origin-s2i-nodejs image.
CentOS based Dockerfile with 64bit Node.js binaries from nodejs.org. Used to create the
CentOS based Dockerfile with 64bit Node.js binaries from nodejs.org.
Folder containing scripts which are responsible for the build and test actions performed by the
Use this file to add these runtimes to OpenShift's web-based "Add to Project" workflow.
A JSON file containing metadata about the releases currently supported.
This folder contains scripts that are run by
Used to install the sources into the location where the application will be run and prepare the application for deployment (eg. installing modules using npm, etc.)
This script is responsible for running the application, by using the application web server.
This script prints the usage of this image.
This folder contains a file with commonly used modules.
This folder contains the
s2itest framework with simple Node.js echo server, an onbuild test and onbuild test with openshift using
oc cluster up.
See the build your own builder images section of the