arm64v8/lightstreamer repository overview

Note: this is the "per-architecture" repository for the arm64v8 builds of the lightstreamer official image⁠ -- for more information, see "Architectures other than amd64?" in the official images documentation⁠ and "An image's source changed in Git, now what?" in the official images FAQ⁠.

⁠Quick reference

• Maintained by:
  the Lightstreamer Server Development Team⁠

• Where to get help:
  the Docker Community Slack⁠, Server Fault⁠, Unix & Linux⁠, or Stack Overflow⁠

⁠Supported tags and respective Dockerfile links

• 6.0.3-jdk8, 6.0-jdk8, 6.0.3-jdk8-temurin, 6.0-jdk8-temurin, 6.0.3, 6.0⁠

• 6.0.3-jdk8-base, 6.0-jdk8-base, 6.0.3-jdk8-temurin-base, 6.0-jdk8-temurin-base, 6.0.3-base, 6.0-base⁠

• 6.1.0-jdk8, 6.1-jdk8, 6.1.0-jdk8-temurin, 6.1-jdk8-temurin, 6-jdk8, 6-jdk8-temurin, 6.1.0, 6.1, 6⁠

• 6.1.0-jdk8-base, 6.1-jdk8-base, 6.1.0-jdk8-temurin-base, 6.1-jdk8-temurin-base, 6-jdk8-base, 6-jdk8-temurin-base, 6.1.0-base, 6.1-base, 6-base⁠

• 7.0.3-jdk8, 7.0-jdk8, 7.0.3-jdk8-temurin, 7.0-jdk8-temurin⁠

• 7.0.3-jdk8-base, 7.0-jdk8-base, 7.0.3-jdk8-temurin-base, 7.0-jdk8-temurin-base⁠

• 7.0.3-jdk11, 7.0-jdk11, 7.0.3-jdk11-temurin, 7.0-jdk11-temurin, 7.0.3, 7.0⁠

• 7.0.3-jdk11-base, 7.0-jdk11-base, 7.0.3-jdk11-temurin-base, 7.0-jdk11-temurin-base, 7.0.3-base, 7.0-base⁠

• 7.1.3-jdk8, 7.1-jdk8, 7.1.3-jdk8-temurin, 7.1-jdk8-temurin⁠

• 7.1.3-jdk8-base, 7.1-jdk8-base, 7.1.3-jdk8-temurin-base, 7.1-jdk8-temurin-base⁠

• 7.1.3-jdk11, 7.1-jdk11, 7.1.3-jdk11-temurin, 7.1-jdk11-temurin, 7.1.3, 7.1⁠

• 7.1.3-jdk11-base, 7.1-jdk11-base, 7.1.3-jdk11-temurin-base, 7.1-jdk11-temurin-base, 7.1.3-base, 7.1-base⁠

• 7.2.2-jdk8, 7.2-jdk8, 7.2.2-jdk8-temurin, 7.2-jdk8-temurin⁠

• 7.2.2-jdk8-base, 7.2-jdk8-base, 7.2.2-jdk8-temurin-base, 7.2-jdk8-temurin-base⁠

• 7.2.2-jdk11, 7.2-jdk11, 7.2.2-jdk11-temurin, 7.2-jdk11-temurin, 7.2.2, 7.2⁠

• 7.2.2-jdk11-base, 7.2-jdk11-base, 7.2.2-jdk11-temurin-base, 7.2-jdk11-temurin-base, 7.2.2-base, 7.2-base⁠

• 7.3.3-jdk8, 7.3-jdk8, 7.3.3-jdk8-temurin, 7.3-jdk8-temurin⁠

• 7.3.3-jdk8-base, 7.3-jdk8-base, 7.3.3-jdk8-temurin-base, 7.3-jdk8-temurin-base⁠

• 7.3.3-jdk11, 7.3-jdk11, 7.3.3-jdk11-temurin, 7.3-jdk11-temurin⁠

• 7.3.3-jdk11-base, 7.3-jdk11-base, 7.3.3-jdk11-temurin-base, 7.3-jdk11-temurin-base⁠

• 7.3.3-jdk17, 7.3-jdk17, 7.3.3-jdk17-temurin, 7.3-jdk17-temurin, 7.3.3, 7.3⁠

• 7.3.3-jdk17-base, 7.3-jdk17-base, 7.3.3-jdk17-temurin-base, 7.3-jdk17-temurin-base, 7.3.3-base, 7.3-base⁠

• 7.4.8-jdk8, 7.4-jdk8, 7.4.8-jdk8-temurin, 7.4-jdk8-temurin, 7-jdk8, 7-jdk8-temurin⁠

• 7.4.8-jdk8-base, 7.4-jdk8-base, 7.4.8-jdk8-temurin-base, 7.4-jdk8-temurin-base, 7-jdk8-base, 7-jdk8-temurin-base⁠

• 7.4.8-jdk11, 7.4-jdk11, 7.4.8-jdk11-temurin, 7.4-jdk11-temurin, 7-jdk11, 7-jdk11-temurin⁠

• 7.4.8-jdk11-base, 7.4-jdk11-base, 7.4.8-jdk11-temurin-base, 7.4-jdk11-temurin-base, 7-jdk11-base, 7-jdk11-temurin-base⁠

• 7.4.8-jdk17, 7.4-jdk17, 7.4.8-jdk17-temurin, 7.4-jdk17-temurin, 7-jdk17, 7-jdk17-temurin⁠

• 7.4.8-jdk17-base, 7.4-jdk17-base, 7.4.8-jdk17-temurin-base, 7.4-jdk17-temurin-base, 7-jdk17-base, 7-jdk17-temurin-base⁠

• 7.4.8-jdk21, 7.4-jdk21, 7.4.8-jdk21-temurin, 7.4-jdk21-temurin, 7-jdk21, 7-jdk21-temurin⁠

• 7.4.8-jdk21-base, 7.4-jdk21-base, 7.4.8-jdk21-temurin-base, 7.4-jdk21-temurin-base, 7-jdk21-base, 7-jdk21-temurin-base⁠

• 7.4.8-jdk25, 7.4-jdk25, 7.4.8-jdk25-temurin, 7.4-jdk25-temurin, 7-jdk25, 7-jdk25-temurin, 7.4.8, 7.4, 7, latest⁠

• 7.4.8-jdk25-base, 7.4-jdk25-base, 7.4.8-jdk25-temurin-base, 7.4-jdk25-temurin-base, 7-jdk25-base, 7-jdk25-temurin-base, 7.4.8-base, 7.4-base, 7-base, base⁠

⁠Quick reference (cont.)

• Where to file issues:
  https://github.com/Lightstreamer/Docker/issues⁠

• Supported architectures: (more info⁠)
  amd64⁠, arm64v8⁠

• Published image artifact details:
  repo-info repo's repos/lightstreamer/ directory⁠ (history⁠)
  (image metadata, transfer size, etc)

• Image updates:
  official-images repo's library/lightstreamer label⁠
  official-images repo's library/lightstreamer file⁠ (history⁠)

• Source of this description:
  docs repo's lightstreamer/ directory⁠ (history⁠)

⁠What is Lightstreamer Server?

Lightstreamer is a real-time messaging server optimized for the Internet. Blending WebSockets, HTTP, and push notifications, it streams data to/from mobile, tablet, browser-based, desktop, and IoT applications.

For more information and related downloads for Lightstreamer Server and other Lightstreamer products, please visit www.lightstreamer.com⁠.

⁠How to use this image

⁠Image editions

Every version is published as two editions:

• arm64v8/lightstreamer:<version> (aliased as latest) — the full server. Runs standalone out of the box; use this to try Lightstreamer out or for one-off deployments.
• arm64v8/lightstreamer:<version>-base (aliased as base) — a leaner image intended as a starting point for integrators building a customized Lightstreamer image. The factory config XMLs, welcome page, demo adapters, and PDF documentation are stripped, so the server will not start standalone — downstream images must supply their own conf/*.xml (and any adapters they need).

Two paths follow — pick one:

• Running the image as-is? → see Running the full image below.
• Packaging a self-contained custom image? → see Packaging a custom image below.

⁠Running the full image

Launch the container with the default configuration:

$ docker run --name ls-server -d -p 80:8080 arm64v8/lightstreamer

This will map port 8080 inside the container to port 80 on the host. Point your browser at http://localhost to watch the Welcome page showing real-time data flowing in from the bundled demo application — a first overview of Lightstreamer's features. More examples are available at the demo site⁠.

⁠File permissions for bind mounts

The container runs as UID 10000 and GID 10000 (and is a member of GID 0 for OpenShift compatibility). Any host file or directory you bind-mount must be readable by that user — either grant read (and traverse for directories) on the host path with chmod -R +rX /path, or use the Packaging a custom image approach below (which lets you assign ownership via COPY --chown=lightstreamer:root).

⁠Custom configuration

Supply a specific configuration file:

$ docker run --name ls-server -v /path/to/my-lightstreamer_conf.xml:/lightstreamer/conf/lightstreamer_conf.xml -d -p 80:8080 arm64v8/lightstreamer

Supply a custom logging configuration together with a host-side logs directory (useful for persistence and I/O performance):

$ docker run --name ls-server -v /path/to/my-lightstreamer_log_conf.xml:/lightstreamer/conf/lightstreamer_log_conf.xml -v /path/to/logs:/lightstreamer/logs -d -p 80:8080 arm64v8/lightstreamer

For the full list of settings, read the inline documentation in lightstreamer_conf.xml and lightstreamer_log_conf.xml under /lightstreamer/conf/ inside the container.

⁠Custom Adapter Sets

Attach a single custom Adapter Set to the factory adapters folder:

$ docker run --name ls-server -v /path/to/my-adapter-set:/lightstreamer/adapters/my-adapter-set -d -p 80:8080 arm64v8/lightstreamer

Or replace the whole factory adapters folder with your own:

$ docker run --name ls-server -v /path/to/my-adapters:/lightstreamer/adapters -d -p 80:8080 arm64v8/lightstreamer

The host directory must follow the layout Lightstreamer expects:

/path/to/my-adapters/
├── my_adapter_set_1/
├── my_adapter_set_2/
└── my_adapter_set_N/

⁠Custom web server pages

Replace the factory pages folder with your own:

$ docker run --name ls-server -v /path/to/custom/pages:/lightstreamer/pages -d -p 80:8080 arm64v8/lightstreamer

⁠Packaging a custom image

To build a self-contained custom image that carries only your own configuration and adapters — with no factory content in the production layer — start from the -base edition. The factory configuration, welcome page, and demo adapters are stripped, so any required file you forget to supply becomes an explicit startup failure rather than a silent fall-back to a factory default.

Alternatively, use FROM arm64v8/lightstreamer (the full edition) as your base: same Dockerfile pattern below, except your custom files land alongside the factory content, and missing configuration files won't cause a startup failure (the server falls back to the factory defaults instead). This is what most customers do; -base is just the leaner option.

The -base image keeps the conf/ directory in place but empties out its factory *.xml files. You must populate it with at least lightstreamer_conf.xml (invoked directly by the launch script), plus the logging and edition configurations it references (typically lightstreamer_log_conf.xml and lightstreamer_edition_conf.xml). Their exact names and paths can be changed by editing lightstreamer_conf.xml, but the files themselves cannot be skipped.

A typical downstream Dockerfile:

FROM arm64v8/lightstreamer:base

# Factory-level configuration
COPY --chown=lightstreamer:root my-conf/     /lightstreamer/conf/

# Zero or more custom Adapter Sets
COPY --chown=lightstreamer:root my-adapter/  /lightstreamer/adapters/my-adapter/

# Optional: custom web server pages
COPY --chown=lightstreamer:root my-pages/    /lightstreamer/pages/

Two notes on the Dockerfile above:

• --chown=lightstreamer:root matches the ownership pattern already used inside the image and keeps everything readable both under plain Docker (USER 10000:10000) and under OpenShift-style deployments (arbitrary UID with GID 0).
• COPY my-conf/ /lightstreamer/conf/ is one convenient way to populate the required configuration files at once; you can also COPY files individually if that better fits your build layout.

Build and run as usual:

$ docker build -t my-lightstreamer .
$ docker run --name ls-server -d -p 80:8080 my-lightstreamer

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's lightstreamer/ directory⁠.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.