debezium-server-fips

packaged by Chainguard

Chainguard Container for debezium-server-fips

A minimal, Wolfi-based, FIPS-enabled image for Debezium Server, streaming PostgreSQL changes to messaging sinks using the Bouncy Castle FIPS provider.

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/debezium-server-fips:latest

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

Compatibility Notes

This image runs /debezium/run.sh from /debezium as UID 185, as the upstream quay.io/debezium/server image does. Mount configuration at /debezium/config and persist offsets under /debezium/data, the same volumes upstream uses.

This image differs from upstream in its runtime:

• Only /debezium/config, /debezium/data and /debezium/jmx are writable, by UID 185 or group 0. Upstream makes all of /debezium world-writable. Run as group 0 (the OpenShift default), or mount /debezium/data from a volume your group can write, such as one with a Kubernetes fsGroup.
• The image ships a JRE without curl or JDK diagnostic tools such as jcmd and jstack. Use an HTTP probe on /q/health instead of an exec healthcheck that calls curl.

The OpenTelemetry agent is attached by default (OTEL_ENABLED=true) and reads its JMX rules from /debezium/config/debezium-jmx-config.yaml. To mount a whole volume at /debezium/config, include that file or set OTEL_ENABLED=false; to add only application.properties, mount it as a single file.

FIPS support

The debezium-server-fips variant uses the Bouncy Castle FIPS provider and ships only the components that can run on it:

• The PostgreSQL source connector is the only source connector. It refuses MD5 authentication; SCRAM-SHA-256, cleartext password, trust, certificate and Kerberos (GSS) authentication remain available. SCRAM passwords must be at least 14 characters, since Bouncy Castle FIPS rejects PBKDF2 passwords shorter than 112 bits.

• The JDBC and Infinispan sinks are not included.

• The Cassandra and DSE connectors are not included.

• run.sh passes -Djavax.net.ssl.trustStoreType=FIPS so the JVM can read the system trust store. That type also reads BCFKS stores.

• To trust a private CA, build a BCFKS truststore from ca.crt in the current directory with the image's keytool, which needs the Bouncy Castle FIPS jars on its classpath. Its password must be at least 14 characters:

  docker run --rm --user "$(id -u)" -v "$PWD:/trust" --entrypoint keytool \
    cgr.dev/ORGANIZATION/debezium-server-fips:latest \
    -J-cp '-J/usr/share/java/bouncycastle-fips/*' -importcert -noprompt \
    -alias private-ca -file /trust/ca.crt -keystore /trust/trust.bcfks -storetype BCFKS -storepass <password>

  Mount the store and pass it in DEBEZIUM_OPTS, with the application.properties from Getting Started. Setting JMX_HOST and JMX_PORT replaces JAVA_OPTS, so a truststore set there is dropped:

  docker run -d --name debezium-server --network debezium \
    -v "$PWD/application.properties:/debezium/config/application.properties:ro" \
    -v "$PWD/trust.bcfks:/trust/trust.bcfks:ro" \
    -e DEBEZIUM_OPTS="-Djavax.net.ssl.trustStore=/trust/trust.bcfks -Djavax.net.ssl.trustStorePassword=<password>" \
    cgr.dev/ORGANIZATION/debezium-server-fips:latest

Getting Started

Write an application.properties that streams PostgreSQL changes to a Redis stream. It expects PostgreSQL (started with wal_level=logical) and Redis reachable as postgres and redis on a Docker network named debezium:

cat > application.properties <<'EOF'
debezium.sink.type=redis
debezium.sink.redis.address=redis:6379
debezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector
debezium.source.offset.storage.file.filename=data/offsets.dat
debezium.source.database.hostname=postgres
debezium.source.database.port=5432
debezium.source.database.user=postgres
debezium.source.database.password=<password>
debezium.source.database.dbname=postgres
debezium.source.topic.prefix=tutorial
debezium.source.plugin.name=pgoutput
EOF

Run the server with that file mounted:

docker run -d --name debezium-server --network debezium \
  -v "$PWD/application.properties:/debezium/config/application.properties:ro" \
  -p 8080:8080 \
  cgr.dev/ORGANIZATION/debezium-server-fips:latest

Debezium Server also maps DEBEZIUM_* environment variables to properties, for example DEBEZIUM_SINK_TYPE=redis. Health is served at http://localhost:8080/q/health.

To run the server under the Debezium Operator, set spec.image in the DebeziumServer resource to cgr.dev/ORGANIZATION/debezium-server-fips:latest.

Documentation and Resources

• Debezium Server documentation
• Debezium Server source
• 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.