Adopt hardened containers without changing your pipelines, tooling, or environment

Today, we're announcing a batch of updates to Chainguard Containers that make it easier to run hardened images in your existing environment. A secure container only helps if it fits the stack you already run, from your RHEL-based pipelines to your FIPS requirements to your compliance tooling. Until now, those gaps have forced teams to choose between security and compatibility. These updates close them. That includes first-party RPM support for RHEL 9 and RHEL 10 (in preview), new -full image tags that drop in without breaking your pipelines, a CMVP-validated Go Geomys FIPS image, Dependabot support for private cgr.dev registries, and flattened CycloneDX SBOMs your compliance tools can actually ingest. Containers have become the dominant unit of deployment for modern software, and the build process itself has become as much of a liability as the runtime. What goes into the base image, which dependencies get pulled, and how the whole thing gets assembled are decisions with real security consequences. AI workloads, regulated…