deprecated
  • orbs-v3 overview
  • orbs-vm
    • Introduction
    • Get started
    • Dockerfile
      • Working Directory
      • Entry point
      • Health check
    • Status
    • Deployment
  • orbs-lambda
    • Introduction
    • Getting Started
    • Supported Networks
    • Project Structure
    • Lambda Triggers
      • OnSchedule
      • onBlocks
      • onEvent
      • Subscribing To Triggers
    • Writing Your Lambda Function
    • Test And Run Locally
    • Paying For Your Transactions
    • Submit Your Lambda
Powered by GitBook
On this page
  1. orbs-vm
  2. Dockerfile

Entry point

PreviousWorking DirectoryNextHealth check

Last updated 2 years ago

Consider the following line described in the :

COPY ./entrypoint.sh /opt/orbs/service

  • The ORBS-NODE docker orchestrator runs this executable when an ORBS-VM instance is started.

Running the executable at /opt/orbs/service is mandatory. If it is not run, the ORBS-VM container will not start. Please note that "service" is the name of the executable itself, and that is how the docker orchestrator starts the container.

Entrypoint example

As an example, let's write a simple entry point bash executable, which starts a node process.

  1. Create entrypoint.sh (sibling to Dockerfile) shell file containing the following:

#!/bin/sh
npm start

2.. Install Entrypoint in Dockerfile

...
# install entry point executable
COPY ./entrypoint.sh /opt/orbs/service
...

3. Continue to

The legacy orbs-v2 service installation spec can be found

dockerfile
HEALTHCHECK
here