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

Working Directory

PreviousDockerfileNextEntry point

Last updated 2 years ago

FROM node:16-alpine

# standard working directory
WORKDIR /opt/orbs

WORKDIR /opt/orbs

  • It is mandatory to set your container to use this WORKDIR for the sake of unity and order, so that your requirements will be the same as the requirements of other services and ORBS-VMs. The orchestrator mounts this folder to a corresponding folder at the host machine for the sake of exporting status and logs via HTTP.

Read more about and

HEALTHCHECK
Status