peerdb-server

packaged by Chainguard

Chainguard Container for peerdb-server

PeerDB SQL gateway (nexus) — a Postgres-wire compatible frontend for PeerDB.

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-server: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-server image is a drop-in replacement for the upstream ghcr.io/peerdb-io/peerdb-server image. It ships the same PeerDB peerdb-server binary — the nexus SQL gateway that presents a Postgres-wire compatible frontend on port 9900 and routes queries to the peers registered in the PeerDB catalog.

The image runs as the non-root peerdb user (UID 1000) with /home/peerdb as the working directory, and the default entrypoint is /home/peerdb/peerdb-server (a symlink to /usr/bin/peerdb-server), matching the upstream layout. Like other minimal production Chainguard Containers, it does not include a shell or package manager.

This image is not available as a FIPS variant. The nexus crypto stack (rustls/ring/aws-lc-rs plus a statically-linked OpenSSL used for SSH tunneling) spans the entire workspace, so there is no FIPS-validated build path.

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

Getting Started

The gateway needs a running PeerDB catalog (a Postgres database) to connect to. Point it at the catalog with the standard PEERDB_CATALOG_* environment variables:

docker run --rm \
  -e PEERDB_CATALOG_HOST=catalog \
  -e PEERDB_CATALOG_PORT=5432 \
  -e PEERDB_CATALOG_USER=postgres \
  -e PEERDB_CATALOG_PASSWORD=postgres \
  -e PEERDB_CATALOG_DATABASE=postgres \
  -e PEERDB_PASSWORD=peerdb \
  -p 9900:9900 \
  cgr.dev/ORGANIZATION/peerdb-server:latest

Once it is up, connect to the gateway with any Postgres client and issue PeerDB commands over the wire protocol:

PGPASSWORD=peerdb psql -h 127.0.0.1 -p 9900 -U peerdb -d peerdb -c "SHOW peers;"

PeerDB is normally deployed as a stack. Use the upstream PeerDB deployment files for your selected version, then override the peerdb-server image with its Chainguard equivalent.

Documentation and Resources

• PeerDB documentation — configuring peers, mirrors, and the SQL gateway.
• PeerDB-io/peerdb — the upstream source repository.
• nexus — the Rust source for the peerdb-server (nexus) SQL gateway.
• ghcr.io/peerdb-io/peerdb-server — 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.