peerdb-ui

packaged by Chainguard

Chainguard Container for peerdb-ui

PeerDB web UI, a Next.js console for managing PeerDB peers and mirrors.

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/peerdb-ui:latest

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

Compatibility Notes

Chainguard's peerdb-ui image is a drop-in replacement for the upstream ghcr.io/peerdb-io/peerdb-ui image. It ships the same PeerDB web console, the Next.js application built in standalone mode, which serves on port 3000 and manages the peers and mirrors registered in the PeerDB catalog.

The image runs as the non-root node user (UID 1000) with /app as the working directory. Its entrypoint is /app/entrypoint.sh, which writes the container environment to /app/.env.production before exec-ing its command, and the default command is node server.js, matching the upstream layout. That entrypoint is a /bin/sh script, so the image ships BusyBox as upstream's Alpine-based image does, but no package manager.

Use the same PeerDB version tag across the UI, peerdb-server, the flow components, and the catalog, because PeerDB is designed to run as one versioned stack.

Getting Started

The UI is a stateless frontend, so point it at a running PeerDB stack through its runtime environment. On its own it still serves the console, where the root path redirects to /peers:

docker run --rm -p 3000:3000 cgr.dev/ORGANIZATION/peerdb-ui:latest

Then open http://localhost:3000 in a browser.

Against a real deployment the console reads its configuration from the environment:

• PEERDB_CATALOG_HOST, PEERDB_CATALOG_PORT, PEERDB_CATALOG_USER, PEERDB_CATALOG_PASSWORD and PEERDB_CATALOG_DATABASE address the PeerDB catalog Postgres, and DATABASE_URL carries the same connection as a single postgres:// URL.
• PEERDB_FLOW_SERVER_HTTP is the base URL of the flow API, for example http://flow-api:8113.
• PEERDB_PASSWORD turns on the console's password sign-in. Leave it unset to serve the console without authentication.
• NEXTAUTH_SECRET signs sessions and NEXTAUTH_URL is the external URL a browser posts logins back to.

Deploying with Helm

PeerDB publishes its enterprise chart from PeerDB-io/peerdb-enterprise. Point the UI slot at this image, keeping the tag aligned with the rest of the stack:

peerdbUI:
  image:
    repository: cgr.dev/ORGANIZATION/peerdb-ui
  version: latest

The chart can deploy its own Temporal, but those setup jobs call tctl, which Chainguard's temporal-admin-tools drops as deprecated in favor of the temporal CLI. Set temporal.deploy.enabled: false and point temporal.host at a Temporal installed separately, such as the Chainguard temporal chart.

Documentation and Resources

• PeerDB documentation covers configuring peers, mirrors, and the console.
• PeerDB-io/peerdb is the upstream source repository.
• ui is the Next.js source for the PeerDB web console.
• ghcr.io/peerdb-io/peerdb-ui is the upstream container image.

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.