Chainguard Container for omni-fips

Omni managing Kubernetes clusters across bare metal, VMs, and cloud

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

Chainguard's omni-fips container image is comparable to the siderolabs/omni image on Docker Hub, with the following differences:

• Like all other Chainguard Containers, omni-fips features a stripped down, minimal design
• It has few-to-zero CVEs

FIPS Support

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

Getting Started

Run the Container

Replace paths to your TLS certs and private keys and adjust parameters as needed:

docker run --rm -it \
  -v /path/to/tls.crt:/tls.crt \
  -v /path/to/tls.key:/tls.key \
  -v /path/to/privatekey.asc:/omni.asc \
  cgr.dev/ORGANIZATION/omni-fips:latest \
  --cert=/tls.crt \
  --key=/tls.key \
  --private-key-source=file:///omni.asc \

• This starts the Omni container with the minimal required configuration.
• The container listens on port 443 by default (you can modify this with --bind-addr).

What to Expect

• The container will start running the omni backend services (API, control plane).
• Logs will output startup success.
• Omni will serve its API and associated services on the bind address.

Accessing the Web UI

• Once the container is running, access the Omni Web UI by navigating to the domain or IP you configured for Omni in your browser.
• If you used the IP or domain omni.example.com and bind address 0.0.0.0:443, visit:

https://omni.example.com/

• If running on localhost for testing and binding to port 443, you can try:

https://localhost/

Documentation and Resources

• Official Omni Documentation
• Omni Getting Started Guide
• Omni CLI Docs - omnictl

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.