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

For a quick test, print the version information:

docker run --rm reg.mini.dev/pg-timetable-fips --version

To try pg_timetable against a real PostgreSQL database, save the following to a compose.yaml file in your working directory:

services:
  postgres:
    image: reg.mini.dev/postgres:latest
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: timetable
    ports:
      - "5432:5432"
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 5s
      timeout: 5s
      retries: 5

  pg-timetable:
    image: reg.mini.dev/pg-timetable-fips:latest
    depends_on:
      postgres:
        condition: service_healthy
    environment:
      PGTT_CONNSTR: "host=postgres port=5432 dbname=timetable user=postgres password=postgres sslmode=disable"
      PGTT_RESTPORT: "8008"
    ports:
      - "8008:8008"
    command:
      - --clientname=demo_worker
      - --upgrade

docker compose up -d

Wait for all services to become healthy:

docker compose ps

pg_timetable creates its own timetable schema in the target database on startup. Confirm it exists:

docker compose exec postgres psql -U postgres -d timetable -c "\dn"

A successful initialization lists the timetable schema alongside public:

   List of schemas
   Name    |       Owner
-----------+--------------------
 public    | pg_database_owner
 timetable | postgres
(2 rows)

Stop and remove all containers and volumes:

docker compose down -v

Technical Considerations

The pg_timetable-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image.

1. Runs as non-root by default for a security-first approach that protects against privilege escalation attacks.
2. Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

• See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
• Review the compliance report to see the default hardening and security configurations for the image.

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.