8.2.0-Main (X8)

The X8 Compose generation as released in August 2026: one image with master, ui, listener and processor roles, Apache Ignite and Hazelcast clustering, an optional Traefik edge, and an .env-driven deployment.

What you will do: know what the X8 stack is, what it requires and how it is upgraded, before you move a deployment to it.

8.2.0-Main is the current X8 release. X8 is the container generation of XPLG: the same products as V7, delivered as a Docker or Podman Compose stack for Linux hosts. It runs beside V7 — a V7 server is still the path for Windows collection and for hosts without containers.

What is in the release

  • One image, four roles. docker.xplg.com/xplg:8.2.0-Main (private registry) or xplghub/images:8.2.0-Main runs as master (one per cluster), ui (web console and REST API), listener, processor and an optional processor-1, selected with COMPOSE_PROFILES on each server.
  • Clustering. Apache Ignite (cluster management group and meta-storage, fixed odd-numbered quorum) and Hazelcast (members listed as alias:port) on host networking; memlock 256 MB.
  • Edge. An optional self-registering Traefik on 80 / 443 / 30303 / 30443 and 8304–8308 in front of the roles; role ports ui 30304, listener 30305, processor 30306, master 30308.
  • Storage. Node state under /node/data on local disk (never NFS); the shared external configuration under /home/data on a path that may be NFS (XPLG_SHARED_HOST_PATH); service uid 30303, gid 0.
  • Operations. .env is the only file you edit (SELF_ALIAS, COMPOSE_PROFILES, XPLG_IMAGE, the seed map, XPLG_BASE_HOST_PATH, XPLG_SHARED_HOST_PATH); xplg-preflight.sh, docker compose config, up -d; first boot takes one to eight minutes; verify.sh checks the roles.
  • Products. PortX, XpoLog, LogX, Flux and Audity as on V7; the console, listeners, forwarders, monitors and apps behave the same.

Requirements

  • Linux host (bare metal, VM or cloud VM) with cgroups v2; Docker Engine with Compose 2.20 or newer, or Podman 4.7 or newer. Kubernetes, OpenShift, Tanzu, Swarm and the managed container services are planned, not supported.
  • Sizing as on System requirements; one region per cluster; NTP on every host.
  • Access to the image registry for the pull; outbound HTTPS to dock for the heartbeat.

Upgrading

  1. Pull the new tag and set XPLG_IMAGE in .env.
  2. docker compose pull, then docker compose up -d on every server; roles restart one by one and keep /node/data and the shared extConf.
  3. Run verify.sh and the five validation phases on Upgrades.

Roll back by restoring the previous tag and running up -d again.

Known limits

  • There is no Kubernetes chart yet; clusters are a data source through Fluent Bit.
  • Windows Events and UNC collection need a Windows node, which means a V7 server or listener.
  • The X8 line has no earlier published release notes; this page is the first entry.

Next: 7.9859

Source: XPLG wiki, pages 3150774276, 3150544899, 3150807046, 3151953922, 3151659011, 1595637899 (https://xpolog.atlassian.net/wiki/spaces/XPOL/pages/3150774276).