flow-snapshot-worker

packaged by Chainguard

Chainguard Container for flow-snapshot-worker

PeerDB Flow Snapshot Worker

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/flow-snapshot-worker: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 flow-snapshot-worker Chainguard Image is a drop-in replacement for the upstream ghcr.io/peerdb-io/flow-snapshot-worker image, with the following differences:

• Uses Chainguard's hardened Wolfi base instead of Alpine Linux
• Includes only the minimal dependencies required to run the snapshot worker
• Runs as a non-root user (peerdb with UID/GID 65532)
• Provides both standard and -dev variants for debugging
• Smaller attack surface with fewer packages and vulnerabilities

The image maintains full compatibility with PeerDB's snapshot worker functionality and configuration.

Getting Started

The flow-snapshot-worker processes snapshot tasks in the PeerDB data synchronization pipeline. It connects to a PostgreSQL catalog database and Temporal workflow engine to execute snapshot operations.

Basic Usage

To run the snapshot worker, you'll need to provide connection details for both the catalog database and Temporal:

docker run --rm \
  -e PEERDB_CATALOG_HOST=postgres \
  -e PEERDB_CATALOG_PORT=5432 \
  -e PEERDB_CATALOG_USER=postgres \
  -e PEERDB_CATALOG_PASSWORD=postgres \
  -e PEERDB_CATALOG_DATABASE=postgres \
  -e TEMPORAL_HOST_PORT=temporal:7233 \
  -e PEERDB_TEMPORAL_NAMESPACE=default \
  cgr.dev/chainguard/flow-snapshot-worker:latest

Using with PeerDB Stack

For a complete PeerDB deployment, see the official docker-compose.yml. To use Chainguard images:

1. Replace ghcr.io/peerdb-io/flow-snapshot-worker:stable-v0.30.9 with cgr.dev/chainguard/flow-snapshot-worker:latest
2. Replace other PeerDB components with their Chainguard equivalents as available

Configuration

The snapshot worker is configured through environment variables:

Required Configuration

• PEERDB_CATALOG_HOST: PostgreSQL host for the PeerDB catalog
• PEERDB_CATALOG_PORT: PostgreSQL port (default: 5432)
• PEERDB_CATALOG_USER: Database username
• PEERDB_CATALOG_PASSWORD: Database password
• PEERDB_CATALOG_DATABASE: Database name
• TEMPORAL_HOST_PORT: Temporal server address (format: host:port)

Optional Configuration

• PEERDB_TEMPORAL_NAMESPACE: Temporal namespace (default: default)
• RUST_LOG: Logging level (options: error, warn, info, debug, trace)
• PEERDB_VERSION_SHA_SHORT: Version identifier for deployments
• AWS_ACCESS_KEY_ID: AWS credentials for S3 staging (if using S3)
• AWS_SECRET_ACCESS_KEY: AWS secret key
• AWS_REGION: AWS region
• AWS_ENDPOINT: Custom S3 endpoint for compatible storage

Documentation and Resources

• PeerDB Documentation
• Temporal Workflow Documentation
• Chainguard Academy - Container Images

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.