fortio-fips

packaged by Chainguard

Chainguard Container for fortio-fips

A minimal Wolfi-based FIPS-enabled image for Fortio, a load-testing tool, advanced echo server, and web UI for HTTP, gRPC, TCP and UDP.

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/fortio-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 is the FIPS-enabled variant of the Chainguard fortio image. Like most other Chainguard Images, this image has few-to-zero CVEs and runs as the non-root user fortio (UID/GID 65532) rather than root.

If you want to use the image with a shell and package manager, you can use the -dev variant of this image.

Fortio's server mode exposes the following ports by default:

FIPS Support

The fortio-fips Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module, so all cryptographic operations (including TLS and gRPC-over-TLS) use only FIPS-approved algorithms.

For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

Server mode

By default the container starts Fortio in server mode:

docker run --rm -p 8080:8080 -p 8079:8079 -p 8078:8078 -p 8081:8081 \
  cgr.dev/ORGANIZATION/fortio-fips:latest

Open the web UI at http://localhost:8080/fortio/, or exercise the debug echo endpoint, which reflects the request back as readable text:

curl --data "hello from fortio" "http://localhost:8080/debug/echo/"

The sized echo endpoint (/echo?size=N) returns N raw bytes of body, so redirect it rather than printing it to your terminal:

curl -s "http://localhost:8080/echo?size=128" | wc -c   # 128

Load testing

Because Fortio is the entrypoint, you can override the default server command with any Fortio subcommand. For example, to run an HTTP load test:

docker run --rm cgr.dev/ORGANIZATION/fortio-fips:latest \
  load -qps 50 -c 8 -t 10s https://example.com/

Run a gRPC ping load test against a Fortio server:

docker run --rm cgr.dev/ORGANIZATION/fortio-fips:latest \
  load -grpc -ping -c 2 -n 100 fortio-server:8079

Kubernetes

Fortio is commonly deployed as a long-running echo server and web UI for on-cluster load testing:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: fortio
  labels:
    app: fortio
spec:
  replicas: 1
  selector:
    matchLabels:
      app: fortio
  template:
    metadata:
      labels:
        app: fortio
    spec:
      containers:
      - name: fortio
        image: cgr.dev/ORGANIZATION/fortio-fips:latest
        ports:
        - containerPort: 8080
          name: http
        - containerPort: 8079
          name: grpc
        - containerPort: 8078
          name: tcp-udp
---
apiVersion: v1
kind: Service
metadata:
  name: fortio
  labels:
    app: fortio
spec:
  selector:
    app: fortio
  ports:
  - port: 8080
    targetPort: 8080
    name: http
  - port: 8079
    targetPort: 8079
    name: grpc

Save the manifest above as fortio.yaml, then apply it and wait for the deployment to become ready:

kubectl apply -f fortio.yaml
kubectl rollout status deployment/fortio --timeout=120s

Documentation and Resources

• Fortio GitHub repository
• Fortio documentation
• Fortio command-line reference

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.