Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Request trialMinimalist Wolfi-based Cosign image for signing and verifying images using Sigstore.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
Like most other Chainguard Images, Chainguard's cosign-fips
Container image has few-to-zero CVEs and does not run as the root user.
The cosign-fips
Chainguard Container 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
You can use the cosign-fips
Container image image to sign and verify container images via Docker or through automated workflows such as GitHub Actions.
To verify an image signature, use the image to run Cosign's verify
command. As of Cosign 2.0, Cosign defaults to using Sigstore's keyless mode, you'll need to also specify the OIDC issuer and signer identity to tell Cosign who you trust for the verification process.
For convenience, you can export those values as environment variables in your shell, and then tell Docker to pass those environment variables into the running Cosign container:
The following example uses the cosign-fips
Container image to verify the signature of the Cosign image itself:
The following GitHub Action will log into the registry, push an image, and then sign it with Cosign:
Another common use case for Cosign is attesting to an image's SBOM (software bill of materials). The following command creates an attestation of type spdxjson
for an image based on the provided SBOM file and image digest:
A detailed guide on how to sign an SBOM with Cosign is available on Chainguard Academy.
Cosign can also be used to verify the identity of the person or entity issuing an attestation. To verify that an attestation was issued by a specific entity, we use the cosign verify-attestation
command, specifying the email address of the issuer:
If the identity is successfully verified, an initial message similar to the following is printed to stderr:
The following environment variables are required when verifying a container image signature:
COSIGN_CERTIFICATE_OIDC_ISSUER
: Trusted OIDC issuer, example: https://token.actions.githubusercontent.com
COSIGN_CERTIFICATE_IDENTITY
: Trusted certificate identity, example: https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main
To obtain detailed information about the environment, you can run the cosign env
command:
You'll get output similar to this, containing the environment variables used to configure Cosign:
Chainguard Academy: Verifying Chainguard Images and Metadata Signatures with Cosign
Video: Signing and Verifying Container Images With Sigstore Cosign and Kyverno
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:
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.
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.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
GCC-exception-3.1
GPL-2.0-only
GPL-2.0-or-later
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs