Base JRE 25 + NATS image for the FeatureHub Party Server (build use only)
1.7K
featurehub/base_party is the base image used to build the
FeatureHub Party Server. You don't run it directly. It is the
FROM image that the Party Server's Maven build (Google Jib) layers the application onto.
It is the same as featurehub/base_jdk plus a NATS server.
The Party Server starts that NATS server internally, so a single container provides the Admin app, the Management
Repository, the Dacha2 cache and Edge with streaming.
See Option 1a – Low Volume Deployment.
To run FeatureHub, see the documentation at https://docs.featurehub.io.
eclipse-temurin:25-jre-alpine)/target/nats-server (taken from the official nats:2.12-alpine image), with its
config at /etc/nats/nats-server.confk8suser with UID/GID 999. The Party Server runs as --user 999:999.| Directory | Purpose |
|---|---|
/etc/common-config | Default configuration and log4j2.xml baked into the Party Server image |
/etc/app-config | Where you mount application.properties and secrets.properties. See Run configuration. |
/db | Data directory, used for the H2 database in evaluation setups |
/target | Bundled binaries (NATS) |
Exposed ports: 8085 (Admin app, MR and Edge) and 8701 (metrics and health).
The image is published for linux/amd64 and linux/arm64.
Tags are base image versions (for example 2.2), not FeatureHub versions. The version the Party Server uses is set
by app.baseimage in backend/party-server/pom.xml.
The source is in pipeline/build/base_party.
To build and push a multi-architecture image (this requires docker buildx and a DockerHub login):
cd pipeline/build/base_party
sh make-dualarch-and-push.sh
When you bump the tag, or update NATS, change it in make-dualarch-and-push.sh and in backend/party-server/pom.xml.
Content type
Image
Digest
sha256:393b206e5…
Size
84.5 MB
Last updated
7 months ago
docker pull featurehub/base_party:2.2