datahub-frontend-react

packaged by Chainguard

Chainguard Container for datahub-frontend-react

DataHub Frontend serves the DataHub React web UI and proxies authenticated requests to DataHub GMS.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/datahub-frontend-react:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard datahub-frontend-react image is comparable to the upstream acryldata/datahub-frontend-react image. It is built from the DataHub source (Java/Scala Play Framework with the bundled React UI, licensed under Apache License 2.0) and keeps the upstream container layout: the distribution is available at /datahub-frontend, the image starts with /bin/sh -c ./start.sh from /, and the OpenTelemetry and Prometheus JMX agents are available at the root-level paths start.sh expects.

The image runs on Java 25, matching upstream and the datahub-gms image.

Like upstream, the image runs as the nonroot datahub user (UID 100, GID 100) with home directory /home/datahub. Application and configuration files are root-owned; mount custom configuration readable by the runtime user. Logs are written under /tmp/datahub/logs/datahub-frontend by default, so /tmp must be writable.

Application dependencies are updated for security fixes. Hazelcast is not included, because the frontend does not use it.

The upstream JMX_VERSION build variable is not set, because it only selects the JMX exporter download during the upstream image build. The JMX exporter is provided by a Chainguard package instead.

Prerequisites

The frontend needs a reachable DataHub GMS service. Set DATAHUB_SECRET (at least 32 characters) and DATAHUB_SYSTEM_CLIENT_SECRET, and point DATAHUB_GMS_HOST and DATAHUB_GMS_PORT at your GMS deployment. Follow the upstream Kubernetes deployment guide for the full platform.

Getting Started

Replace ORGANIZATION with your Chainguard organization and run the frontend against an existing GMS:

docker run --rm -p 9002:9002 -p 4319:4319 \
  -e DATAHUB_GMS_HOST=datahub-gms \
  -e DATAHUB_GMS_PORT=8080 \
  -e DATAHUB_SECRET=replace-with-a-random-secret-of-32-plus-characters \
  -e DATAHUB_SYSTEM_CLIENT_SECRET=replace-with-your-system-client-secret \
  cgr.dev/ORGANIZATION/datahub-frontend-react:latest

Check the liveness endpoint on the management port:

curl -fsS http://localhost:4319/health/live

The management listener on port 4319 (MANAGEMENT_SERVER_PORT, set by start.sh) also serves /health/ready. Use these endpoints for liveness and readiness probes. The /health and /admin routes on the HTTP port are deprecated for probes.

To use the image with the DataHub Helm chart, write the frontend image override to a values file and apply it to an existing release. The example assumes a release named datahub in namespace datahub with its configuration in values.yaml:

cat > frontend-values.yaml <<EOF
datahub-frontend:
  image:
    registry: cgr.dev
    repository: ORGANIZATION/datahub-frontend-react
    tag: "x.y.z"
EOF

helm repo add datahub https://helm.datahubproject.io
helm upgrade datahub datahub/datahub \
  --namespace datahub \
  --values values.yaml \
  --values frontend-values.yaml \
  --wait --timeout 15m

Configuration

The image sets these environment variables by default:

• SERVER_PORT=9002: the HTTP port the frontend listens on.
• MFE_CONFIG_FILE_PATH=/datahub-frontend/conf/mfe.config.dev.yaml: the micro-frontend configuration file.
• OTEL_EXPORTER_OTLP_*: OpenTelemetry exporter payload, frame size, and compression settings matching upstream.

start.sh sets MANAGEMENT_SERVER_PORT=4319 by default for the management listener that serves /health/live and /health/ready.

Set ENABLE_OTEL=true or ENABLE_PROMETHEUS=true to attach the OpenTelemetry agent or the Prometheus JMX exporter (port 4318). Use JAVA_MEMORY_OPTS to override the default JVM heap settings.

Documentation and Resources

• DataHub documentation
• DataHub Helm charts
• DataHub frontend source

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.