buildpack-deps

packaged by Chainguard

Chainguard Container for buildpack-deps

Common build dependencies: compilers, SCM clients, and dev headers for building software

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/buildpack-deps: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 buildpack-deps Chainguard image is built as an alternative to the buildpack-deps official image from Docker Hub. Where the upstream image publishes one tag per Debian or Ubuntu release, this image is built on Chainguard OS, so a single image covers all of them.

The image bundles the GCC toolchain and make (through build-base), the autotools (autoconf, automake, libtool), version control clients (git, mercurial, subversion, openssh-client), network tools (curl, wget, gnupg), and development headers for commonly linked libraries such as OpenSSL, libcurl, zlib, bzip2, libffi, GMP, readline, SQLite, ncurses, libxml2, libxslt, libyaml, PostgreSQL, MariaDB, Kerberos, libevent, Berkeley DB, libjpeg-turbo, libpng, libwebp, libmaxminddb, and ImageMagick.

Like the upstream image, this image includes a shell and runs bash by default. Unlike the upstream image, it runs as the nonroot user (UID 65532) by default and does not include a package manager. If you need a package manager, use the -dev variant of this image.

Getting Started

Start an interactive shell in the image:

docker run --rm -it cgr.dev/ORGANIZATION/buildpack-deps:latest

To build a project in your current directory, mount it into the container. Because the image runs as UID 65532, the mounted directory must be writable by that user:

docker run --rm -v "${PWD}:/work" -w /work cgr.dev/ORGANIZATION/buildpack-deps:latest \
  bash -c './configure && make'

Usage in a Dockerfile

buildpack-deps is designed as a build stage. The following multi-stage Dockerfile compiles a C program and copies the result into a minimal runtime image:

FROM cgr.dev/ORGANIZATION/buildpack-deps:latest AS builder
WORKDIR /tmp/build
COPY hello.c .
RUN gcc -o hello hello.c

FROM cgr.dev/ORGANIZATION/glibc-dynamic:latest
COPY --from=builder /tmp/build/hello /usr/bin/hello
ENTRYPOINT ["/usr/bin/hello"]

Documentation and Resources

• Upstream buildpack-deps repository
• Chainguard Academy: Choosing an Image for your Compiled Programs

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.