Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpBuildkit is a concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit.
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.
The Chainguard buildkit-fips
container image is comparable to the upstream BuildKit image maintained by Moby. As with other Chainguard Containers, the buildkit-fips
image was designed with minimalism in mind, and therefore doesn't contain things like a shell or package manager.
The buildkit-fips
Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.
You can use the buildkit-fips
container image to run the BuildKit daemon with the following command:
This example includes the -d
flag which tells Docker to run the container in the background.
Next, create a BUILDKIT_HOST
environment variable, specifying the running container's address. This will set the BuildKit daemon as your remote builder:
Following that you can use the containerized daemon. As an example, create a Dockerfile:
Then run the following command to build an image using this Dockerfile:
You can also run the client and an ephemeral daemon in a single container. The BuildKit project refers to this method as "daemonless mode."
This method depends on using the buildctl-daemonless.sh
script. Because Chainguard's standard buildkit-fips
variant does not have a shell, you will need to use the development variant to use daemonless mode.
Again, if you don't already have a Dockerfile you can create one with the following command:
Then run a command like the following to build an image using this Dockerfile:
This example mounts the working directory to the container's /tmp/work
directory and specifies the buildctl-daemonless.sh
script as the entrypoint. Again, be sure to specify the latest-dev
development variant of the buildkit-fips
image.
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-3.0-or-later
LGPL-2.1-or-later
MIT
MPL-2.0
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