Chainguard Container for buildkit-fips

Buildkit is a concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit.

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/buildkit-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 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.

FIPS Support

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.

Getting Started

You can use the buildkit-fips container image to run the BuildKit daemon with the following command:

docker run -d --name buildkitd --privileged cgr.dev/ORGANIZATION/buildkit-fips:latest

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:

export BUILDKIT_HOST=docker-container://buildkitd

Following that you can use the containerized daemon. As an example, create a Dockerfile:

cat > Dockerfile <<EOF
FROM scratch
EOF

Then run the following command to build an image using this Dockerfile:

buildctl build \
	--frontend=dockerfile.v0 \
	--local context=. \
	--local dockerfile=.

[+] Building 0.0s (2/2) FINISHED                                                         	 
 => [internal] load build definition from Dockerfile                                 	0.0s
 => => transferring dockerfile: 51B                                                  	0.0s
 => [internal] load .dockerignore                                                    	0.0s
 => => transferring context: 34B

Daemonless mode

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:

cat > Dockerfile <<EOF
FROM scratch
EOF

Then run a command like the following to build an image using this Dockerfile:

docker run \
  --rm \
  --privileged \
  -v $(pwd):/tmp/work \
  --entrypoint buildctl-daemonless.sh \
  cgr.dev/ORGANIZATION/buildkit-fips:latest-dev \
  	build \
  	--frontend dockerfile.v0 \
  	--local context=/tmp/work \
  	--local dockerfile=/tmp/work

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 51B done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 transferring context: 34B done
#2 DONE 0.0s

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.

Documentation and Resources

• BuildKit Documentation
• BuildKit GitHub Repository

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.