Chainguard Container for apache-hop-fips

Data orchestration and engineering platform for managing ETL/ELT workflows.

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/apache-hop-fips:latest

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

FIPS Compliance

The apache-hop-fips Chainguard Image ships with a validated redistribution of the Bouncy Castle FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

FIPS Configuration Details

This image is pre-configured with the following FIPS-specific settings:

• Module Path: The Bouncy Castle FIPS provider is automatically configured via JAVA_TOOL_OPTIONS with --module-path=/usr/share/java/bouncycastle-fips
• Trust Store Type: Default trust store type is set to BCFKS for FIPS compliance
• Key Store Type: Supports BCFKS keystore format for secure key management
• CLASSPATH: Pre-configured to include FIPS provider libraries at /usr/share/java/bouncycastle-fips/* and /opt/hop/lib/fips/*

These settings ensure the container operates in FIPS-compliant mode without requiring additional configuration.

Usage

Running with Docker

docker run -d \
  -p 8081:8081 \
  -e HOP_SERVER_USER=admin \
  -e HOP_SERVER_PASS=admin \
  cgr.dev/ORGANIZATION/apache-hop-fips:latest

Kubernetes Deployment

Deploy with Helm using FIPS configuration:

# Add the Apache Hop repository
helm repo add hop https://hop.apache.org/
helm repo update

# Create values file for FIPS deployment
cat <<EOF > values-fips.yaml
server:
  image:
    name: cgr.dev/ORGANIZATION/apache-hop-fips
    tag: latest
EOF

# Install with FIPS configuration
helm install apache-hop-fips hop/hop -f values-fips.yaml

For detailed documentation on Apache Hop, visit the official Apache Hop documentation.

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.