oras-fips

packaged by Chainguard

Chainguard Container for oras-fips

FIPS-validated build of the ORAS (OCI Registry As Storage) CLI. Same surface as the standard oras image, compiled against the Go-FIPS toolchain and BoringCrypto so cryptographic operations (TLS to the registry, signature verification) run in a FIPS 140 mode.

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/oras-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

The oras-fips image is a drop-in replacement for the non-FIPS oras image — same entrypoint (/bin/oras), same working directory (/workspace), same CLI surface. The only difference is that the ORAS binary is compiled against Chainguard's Go-FIPS toolchain and ships alongside openssl-config-fipshardened, so TLS connections to remote registries and any signature-verification path go through a FIPS 140 validated cryptographic provider.

Getting started

ORAS usage is identical to the standard image. For example, push a file as an OCI artifact to a local layout store:

mkdir oras-demo && cd oras-demo
echo "hello oras-fips" > artifact.txt
docker run --rm -v "$(pwd):/workspace" cgr.dev/ORGANIZATION/oras-fips:latest \
  push --oci-layout demo-store:v1 artifact.txt

Documentation and Resources

• ORAS project documentation
• CLI command reference
• GitHub repository

FIPS Support

The oras-fips Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

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.