Skip to content

docker.md

Latest commit

 

History

History
87 lines (66 loc) · 3.52 KB

docker.md

File metadata and controls

87 lines (66 loc) · 3.52 KB
Raw

Running erpl-rev with Docker

Each release publishes a linux/amd64 container image to GitHub Container Registry, tagged with the release version and latest:

ghcr.io/datazoode/erpl-rev:latest        # newest release
ghcr.io/datazoode/erpl-rev:<version>     # a specific release, e.g. 2026.06.13

The image bakes the exact erpl-rev-linux-amd64 self-extracting bundle from the same release (server + SAP NW RFC SDK libs + ICU + DuckDB). On start the bundle's launcher extracts to a temp dir and sets its own loader path — so the image needs no LD_LIBRARY_PATH, and what you docker pull is the same artifact you'd download. CI smoke-tests the built image (docker run --rm … --smoke) before pushing. It runs as a non-root user (uid 10001) and stores its DuckDB file on a /data volume.

The launcher self-extracts to $TMPDIR (default /tmp) on first run. If you run with a read-only root filesystem, mount a writable emptyDir at /tmp.

Quick start

docker run -d --name erpl-rev \
  -e ERPL_REV_GWHOST=sap-gateway.example.com \
  -e ERPL_REV_GWSERV=sapgw00 \
  -e ERPL_REV_PROGRAM_ID=ERPL_REV \
  -v erpl-data:/data \
  ghcr.io/datazoode/erpl-rev:latest

Add the DuckDB network server (quack) and publish its port:

docker run -d --name erpl-rev \
  -e ERPL_REV_GWHOST=sap-gateway.example.com -e ERPL_REV_GWSERV=sapgw00 \
  -e ERPL_REV_QUACK_TOKEN=<your-token> \
  -v erpl-data:/data -p 9494:9494 \
  ghcr.io/datazoode/erpl-rev:latest --quack --quack-listen quack:0.0.0.0:9494

Configuration

Everything is driven by environment variables (CLI flags override them):

Env var Default Purpose
ERPL_REV_GWHOST localhost SAP gateway host
ERPL_REV_GWSERV 3300 SAP gateway service (e.g. sapgw00)
ERPL_REV_PROGRAM_ID ERPL_REV registered program id (must match reginfo)
ERPL_REV_REG_COUNT 5 parallel gateway registrations
ERPL_REV_DB_PATH /data/erpl-rev.duckdb DuckDB file (set :memory: for throwaway)
ERPL_REV_QUACK / ERPL_REV_QUACK_LISTEN / ERPL_REV_QUACK_TOKEN off DuckDB network server
ERPL_REV_LOG_LEVEL / ERPL_REV_LOG_FORMAT info / json logging (image defaults to json)
ERPL_REV_NO_TELEMETRY / DATAZOO_DISABLE_TELEMETRY — opt out of telemetry (docs/telemetry.md)

Networking

RFC registration is outbound: the container connects to the SAP gateway and the gateway dispatches RFC calls back over that connection. So:

  • The container needs network reachability to ERPL_REV_GWHOST:ERPL_REV_GWSERV.
  • No inbound RFC port needs publishing. Only -p 9494:9494 if you enable quack.
  • The gateway's reginfo ACL must permit ERPL_REV_PROGRAM_ID from the container host's IP (see docs/enable-rfc-registration.md).

Persistence

The DuckDB file lives at /data/erpl-rev.duckdb. Mount a named volume (or host path) at /data so replicated data survives container restarts.

Verifying the image

--smoke loads the bundled SAP SDK + DuckDB and exits without contacting any gateway — handy as a post-pull sanity check:

docker run --rm ghcr.io/datazoode/erpl-rev:latest --smoke
# -> erpl-rev smoke ok: SAP NW RFC SDK 750 ...; DuckDB {"v":"v1.5.4"}

Notes

  • Platform: linux/amd64 only (the SAP NW RFC SDK is not available for linux/arm64 in our build pipeline).
  • SAP SDK: the image embeds the SAP NW RFC SDK runtime libraries, identical to what the published release bundles already ship.