This repository contains sources files needed to build the Node.js runtimes for Apache OpenWhisk. The build system will produce a series of docker images for each runtime version. These images are used in the platform to execute Node.js actions.
The following Node.js runtime versions (with kind & image labels) are generated by the build system:
- Node.js 6.17.1 (
nodejs:6
&openwhisk/nodejs6action
) - Node.js 8.16.0 (
nodejs:8
&openwhisk/action-nodejs-v8
) - Node.js 10.15.3 (
nodejs:10
&openwhisk/action-nodejs-v10
) - Node.js 12.1.0 (
nodejs:12
&openwhisk/action-nodejs-v12
)
This README documents the build, customisation and testing of these runtime images.
Do you want to learn more about using Node.js actions to build serverless applications? Please see the main project documentation here for that information.
If the deployment of Apache OpenWhisk includes these images in the runtime manifest, use the --kind
parameter to select the Node.js runtime version.
wsk action update myAction myAction.js --kind nodejs:6
wsk action update myAction myAction.js --kind nodejs:8
wsk action update myAction myAction.js --kind nodejs:10
wsk action update myAction myAction.js --kind nodejs:12
All the runtime images are published by the project to Docker Hub @ https://hub.docker.com/u/openwhisk
- https://hub.docker.com/r/openwhisk/nodejs6action
- https://hub.docker.com/r/openwhisk/action-nodejs-v8
- https://hub.docker.com/r/openwhisk/action-nodejs-v10
- https://hub.docker.com/r/openwhisk/action-nodejs-v12
These images can be used to execute Node.js actions on any deployment of Apache OpenWhisk, even those without those images defined the in runtime manifest, using the --docker
action parameter.
wsk action update myAction myAction.js --docker openwhisk/action-nodejs-v12
If you build a custom version of the images, pushing those an external Docker Hub repository will allow you to use those on the Apache OpenWhisk deployment.
Available runtimes in Apache OpenWhisk are defined using the runtimes manifest in this file: runtimes.json
Modify the manifest and re-deploy the platform to pick up local images changes.
Dockerfiles for runtime images are defined in the core
directory. Each runtime version folder has a custom Dockerfile
and package.json
. If you need to add extra dependencies to a runtime version - modify these files.
The core/nodejsActionBase
folder contains the Node.js app server used to implement the action interface, used by the platform to inject action code into the runtime and fire invocation requests. This common code is used in all runtime versions.
- Run the
distDocker
command to generate local Docker images for the different runtime versions.
./gradlew core:nodejs6Action:distDocker
./gradlew core:nodejs8Action:distDocker
./gradlew core:nodejs10Action:distDocker
./gradlew core:nodejs12Action:distDocker
This will return the following runtime images with the following names: nodejs6action
, action-nodejs-v8
, action-nodejs-v10
and action-nodejs-v12
.
- Install project dependencies from the top-level Apache OpenWhisk project, which ensures correct versions of dependent libraries are available in the Maven cache.
./gradlew install
This command MUST BE run from the directory containing the main Apache OpenWhisk repository, not this repository's directory.
- Build the local Docker images for the runtime versions (see the instructions above).
- Build the custom Docker images used in local testing.
./gradlew tests:dat:docker:nodejs6docker:distDocker
./gradlew tests:dat:docker:nodejs8docker:distDocker
./gradlew tests:dat:docker:nodejs10docker:distDocker
./gradlew tests:dat:docker:nodejs12docker:distDocker
- Run the project tests.
./gradlew :tests:test
Apache OpenWhisk Runtime Node.js is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.