https://github.com/apache/openwhisk-runtime-docker
Apache OpenWhisk SDK for building Docker "blackbox" runtimes
https://github.com/apache/openwhisk-runtime-docker
apache cloud docker faas functions functions-as-a-service openwhisk openwhisk-runtime serverless serverless-architectures serverless-functions
Last synced: 8 months ago
JSON representation
Apache OpenWhisk SDK for building Docker "blackbox" runtimes
- Host: GitHub
- URL: https://github.com/apache/openwhisk-runtime-docker
- Owner: apache
- License: apache-2.0
- Created: 2017-10-05T19:31:46.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2024-09-24T14:21:48.000Z (about 1 year ago)
- Last Synced: 2025-04-03T04:17:03.915Z (9 months ago)
- Topics: apache, cloud, docker, faas, functions, functions-as-a-service, openwhisk, openwhisk-runtime, serverless, serverless-architectures, serverless-functions
- Language: Python
- Homepage: https://openwhisk.apache.org/
- Size: 3.04 MB
- Stars: 25
- Watchers: 28
- Forks: 43
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Apache OpenWhisk runtimes for docker
[](http://www.apache.org/licenses/LICENSE-2.0)
[](https://github.com/apache/openwhisk-runtime-docker/actions/workflows/ci.yaml)
### Give it a try today
Create a zip action with a `exec` in the root of the zip
```
echo \
'#!/bin/bash
echo "{\"message\":\"Hello World\"}"' > exec
```
For the return result, not only support `dictionary` but also support `array`
```
echo \
'#!/bin/bash
echo '["a", "b"]'' > exec
```
And support array result for sequence action as well, the first action's array result can be used as next action's input parameter
```
echo \
'#!/bin/bash
echo $1' > exec
```
```
chmod +x exec
zip myAction.zip exec
```
Create the action using the docker image for the runtime
```
wsk action update myAction myAction.zip --docker openwhisk/dockerskeleton:1.3.2
```
This works on any deployment of Apache OpenWhisk
### To use on a deployment that contains the runtime deployed
Create action using `--native`
```
wsk action update myAction myAction.zip --native
```
### Local development
```
./gradlew :core:actionProxy:distDocker :sdk:docker:distDocker
```
This will produce the image `whisk/dockerskeleton`
Build and Push image
```
docker login
./gradlew core:actionProxy:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io
```
Deploy OpenWhisk using ansible environment that contains the runtime of type `blackboxes` with name `dockerskeleton`
Assuming you have OpenWhisk already deploy locally and `OPENWHISK_HOME` pointing to root directory of OpenWhisk core repository.
Set `ROOTDIR` to the root directory of this repository.
Redeploy OpenWhisk
```
cd $OPENWHISK_HOME/ansible
ANSIBLE_CMD="ansible-playbook -i ${ROOTDIR}/ansible/environments/local"
$ANSIBLE_CMD setup.yml
$ANSIBLE_CMD couchdb.yml
$ANSIBLE_CMD initdb.yml
$ANSIBLE_CMD wipe.yml
$ANSIBLE_CMD openwhisk.yml
```
Or you can use `wskdev` and create a soft link to the target ansible environment, for example:
```
ln -s ${ROOTDIR}/ansible/environments/local ${OPENWHISK_HOME}/ansible/environments/local-docker
wskdev fresh -t local-docker
```
To use as docker action push to your own dockerhub account
```
docker tag whisk/dockerskeleton $user_prefix/dockerskeleton
docker push $user_prefix/dockerskeleton
```
Then create the action using your image from dockerhub
```
wsk action update myAction myAction.zip --docker $user_prefix/dockerskeleton
```
The `$user_prefix` is usually your dockerhub user id.