FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

Take the Minimus PeerDB-UI-FIPS image for a test run. PeerDB provides an official Docker Compose file that handles all dependency orchestration (Postgres catalog, Temporal, Flow-API, Flow-Worker). The steps below use that upstream setup with Minimus images swapped in.

To begin, log into the Minimus registry:

echo "{token}" | docker login reg.mini.dev -u minimus --password-stdin

Clone the PeerDB repository and create an override file that points to hardened Minimus images:

git clone --depth 1 https://github.com/PeerDB-io/peerdb.git
cd peerdb

Save the following to docker-compose.override.yml:

services:
  catalog:
    image: reg.mini.dev/postgres-fips:latest
  temporal-admin-tools:
    # The upstream mounts a custom entrypoint script and uses the now 
    # deprecated tctl for its healthcheck. Clearing the
    # entrypoint restores the image's built-in CMD, and the healthcheck is
    # replaced with the Temporal CLI.
    image: reg.mini.dev/temporal-admin-tools-fips
    entrypoint: []
    healthcheck:
      test: ["CMD", "temporal", "operator", "cluster", "health", "--address", "temporal:7233"]
      interval: 5s
      timeout: 5s
      retries: 30
      start_period: 45s
  temporal-ui:
    image: reg.mini.dev/temporal-ui-fips
  flow-worker:
    image: reg.mini.dev/peerdb-flow-worker-fips
  flow-snapshot-worker:
    image: reg.mini.dev/peerdb-snapshot-worker-fips
  flow-api:
    image: reg.mini.dev/peerdb-flow-api-fips
  peerdb:
    image: reg.mini.dev/peerdb-server
  peerdb-ui:
    image: reg.mini.dev/peerdb-ui-fips

Print the resolved image list to verify the images:

docker compose config | grep "image:"

Note that Docker Compose will only auto-discover the override file if it is named exactly docker-compose.override.yml or docker-compose.override.yaml. Otherwise you will need to explicitly pass the file names like so:

docker compose -f docker-compose.yml -f my-docker-compose.override.yaml config | grep "image:"

docker compose up -d

Wait for all services to become healthy:

docker compose ps -a

Once the services are running, open the PeerDB-UI dashboard in your browser:

http://localhost:3000

docker compose down -v

Technical Considerations

The PeerDB-UI-FIPS image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Terms & Info

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.