dotstatsuite-supercore

packaged by Chainguard

Chainguard Container for dotstatsuite-supercore

SDMX statistical data API server for the .Stat Suite (super core) backed by ClickHouse and MongoDB

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/dotstatsuite-supercore: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 dotstatsuite-supercore image is comparable to the upstream image published by SIS-CC. Switching to the Chainguard image should not require any changes to your existing setup, aside from the notes below.

Default port

The default port for the dotstatsuite-supercore Chainguard Container is 8080, rather than 80. The container runs as non-root (uid 65532) for security and non-root processes cannot bind to privileged ports (< 1024), so the image ships with SERVER_PORT=8080 set by default. Publish or route to :8080 in your deployment — for example -p 80:8080 on the Docker CLI, or a Kubernetes Service with targetPort: 8080.

Application paths

The application tree is installed at /usr/share/dotstatsuite-supercore/ and exposed at the upstream working directory /opt via the -compat subpackage's symlinks. The shipped runtime paths match the upstream image (/opt/src, /opt/node_modules, /opt/package.json, /opt/yarn.lock, ...), so anything referencing them will continue to work unchanged.

Getting Started

The service needs MongoDB and ClickHouse to function, plus a bucket provider (MinIO / S3 / GCS / Azure) and a config service that serves tenants.json. See the upstream .env.sample for the full list of environment variables.

A minimal docker run against pre-existing backing services:

docker run --rm -p 8080:8080 \
    -e MONGODB_URL=mongodb://mongo:27017 \
    -e MONGODB_DATABASE=sxs \
    -e CLICKHOUSE_URL=http://clickhouse:8123 \
    -e BUCKET_PROVIDER=minio \
    -e MINIO_ENDPOINT=minio -e MINIO_PORT=9000 \
    -e MINIO_ACCESS_KEY=minioadmin -e MINIO_SECRET_KEY=minioadmin \
    -e DATA_BUCKET=data -e MEMBER_DATA_BUCKETS='data-*' \
    -e CONFIG_URL=http://config \
    -e AMQP_URL=amqp://guest:guest@rabbitmq:5672 -e AMQP_DBMX_EXCHANGE=dbmx \
    cgr.dev/ORGANIZATION/dotstatsuite-supercore

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

Once the service is up, GET /healthcheck returns a composite JSON status (mongo, clickhouse, configProvider, tenants) for verifying end-to-end connectivity, alongside GET /healthcheckMongo and GET /healthcheckCH for per-backend checks.

Documentation and Resources

• Upstream .Stat Suite documentation — overall architecture and deployment guidance
• dotstatsuite-supercore upstream repository — SuperCore (sXs) source, .env.sample, and Readme.md
• SDMX standard — the statistical data and metadata exchange standard the service implements

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.