Chainguard Container for minio-iamguarded-fips

MinIO is a high-performance, S3 compatible object store. This FIPS-compliant iamguarded variant is specifically designed to work with the iamguarded Helm chart in FIPS-140 compliant environments.

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/minio-iamguarded-fips:latest

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

Overview

MinIO IAMGuarded FIPS is a security-enhanced, FIPS-140 compliant variant of MinIO designed to be deployed using its companion IAMGuarded Helm chart. This image and chart combination provides additional security benefits over standard MinIO deployments and meets FIPS-140 compliance requirements.

Helm Chart Installation

The MinIO IAMGuarded Helm chart is delivered exclusively through the same OCI registry as your Chainguard images:

cgr.dev/$ORGANIZATION/iamguarded-charts/minio

Basic Installation

Once authenticated you can install the chart with standard Helm commands and your organization name:

helm install minio oci://cgr.dev/$ORGANIZATION/iamguarded-charts/minio \
  --set "global.org=$ORGANIZATION" \
  --set image.repository=cgr.dev/$ORGANIZATION/minio-iamguarded-fips \
  --set clientImage.repository=cgr.dev/$ORGANIZATION/minio-iamguarded-client-fips

Important: Replace $ORGANIZATION with your Chainguard organization name.

To view all available configuration options:

helm show values oci://cgr.dev/$ORGANIZATION/iamguarded-charts/minio

Registry Configuration

For users who mirror images to custom repositories:

• Use global.imageRegistry to override the default cgr.dev
• For complex mirroring strategies, consult the chart's values.yaml for individual image configuration options including registry, repository, tag, and digest

Example values.yaml for individual image configuration:

# Main MinIO server image (FIPS)
image:
  registry: myregistry.example.com
  repository: mirrored/minio-iamguarded-fips
  digest: sha256:... # Use specific digest instead of tag

# MinIO client image (FIPS)
clientImage:
  registry: myregistry.example.com
  repository: mirrored/minio-client-iamguarded-fips
  digest: sha256:... # Use specific digest instead of tag

# OS Shell image for volume permissions (FIPS)
defaultInitContainers:
  volumePermissions:
    enabled: true
    image:
      registry: myregistry.example.com
      repository: mirrored/os-shell-iamguarded-fips
      digest: sha256:... # Use specific digest instead of tag

# MinIO Object Storage image
console:
  registry: myregistry.example.com
  repository: mirrored/minio-object-browser-iamguarded-fips
  digest: sha256:... # Use specific digest instead of tag

Authentication

Ensure proper pull credentials are configured through one of the following methods:

Option 1: Using Helm values with global.imagePullSecrets

# values.yaml
global:
  imagePullSecrets:
    - name: chainguard-pull-secret

Option 2: Create a Kubernetes pull secret

# Step 1: Authenticate with chainctl and generate a pull token
chainctl auth login
chainctl auth configure-docker --pull-token --save --ttl=24h

# Step 2: Create the Kubernetes secret
kubectl create secret docker-registry chainguard-pull-secret \
  --docker-server=cgr.dev \
  --docker-username=$(echo cgr.dev | docker-credential-cgr get | jq -r '.Username') \
  --docker-password=$(echo cgr.dev | docker-credential-cgr get | jq -r '.Secret') \
  -n <your-namespace>

# Step 3: Reference the secret in your Helm installation
helm install minio oci://cgr.dev/$ORGANIZATION/iamguarded-charts/minio \
  --set "global.org=$ORGANIZATION" \
  --set "global.imagePullSecrets[0].name=chainguard-pull-secret"

Option 3: Cluster node-scoped registry permissions (cluster-dependent)

Standalone Docker Usage

While this image is optimized for use with the iamguarded Helm chart, it can also be run standalone:

docker run -p 9000:9000 -p 9001:9001 \
  -e MINIO_ROOT_USER=minio \
  -e MINIO_ROOT_PASSWORD=minio123 \
  cgr.dev/$ORGANIZATION/minio-iamguarded-fips:latest server /data --console-address ":9001"

MinIO Client (FIPS)

The FIPS-compliant MinIO client image is also available:

docker run cgr.dev/$ORGANIZATION/minio-iamguarded-client-fips:latest --help

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.