Chainguard Container for tritonserver-no-backend-fips

The Triton Inference Server provides an optimized cloud and edge inferencing solution.

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/tritonserver-no-backend-fips:latest

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

Overview

This is a FIPS-compliant base image of Triton Inference Server that does not include any pre-installed inference backends. It provides the core Triton server infrastructure (HTTP, GRPC, and metrics services) and CUDA toolkit, with FIPS 140-3 validated cryptography.

For a complete Triton FIPS image with common backends (Python, ONNX Runtime, OpenVINO, TensorRT) pre-installed, see the tritonserver-fips image.

FIPS Support

The tritonserver-no-backend-fips Chainguard Image ships with a validated redistribution of the OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy

Use Cases

This base image is ideal for:

• Custom FIPS-compliant Triton deployments requiring specific backend versions
• Minimizing image size while maintaining FIPS compliance
• Building specialized FIPS-compliant inference servers with custom backend combinations
• Multi-stage Docker builds where backends are added separately to a FIPS-compliant base

Getting Started

Basic Health Check

You can verify the base server functionality with an empty model repository:

docker run -d --name triton-base-fips \
  -p 8000:8000 -p 8001:8001 \
  cgr.dev/ORGANIZATION/tritonserver-no-backend-fips:latest \
  --model-repository=/models

Check server health:

curl http://localhost:8000/v2/health/live
curl http://localhost:8000/v2/health/ready

Query server metadata:

curl http://localhost:8000/v2

Building Custom Images

Use this as a base image to add your own backends while maintaining FIPS compliance:

FROM cgr.dev/ORGANIZATION/tritonserver-no-backend-fips:latest

# Add your custom backends or models
COPY --from=custom-backend /path/to/backend /opt/tritonserver/backends/
COPY models/ /models/

ENTRYPOINT ["/opt/tritonserver/bin/tritonserver"]
CMD ["--model-repository=/models"]

What's Included

• Triton Inference Server core binary
• CUDA 12.9 toolkit
• HTTP, GRPC, and Metrics service infrastructure
• TensorRT binaries (for model conversion utilities)
• FIPS 140-3 validated OpenSSL cryptographic module

What's NOT Included

This image does not include any inference backends. For backend support, you need to:

1. Use the full tritonserver-fips image with pre-installed backends, or
2. Build a custom image layering your required backends on top of this FIPS-compliant base image

Documentation and Resources

• Triton Inference Server Documentation
• Triton Backend Repository
• FIPS-enabled Chainguard Images

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.