buildpack-deps

A collection of common build dependencies used for installing various modules, e.g., gems.

GitHub repo: https://github.com/docker-library/buildpack-deps

Library reference

This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Store page for this image at https://store.docker.com/images/buildpack-deps

Supported tags and respective Dockerfile links

• artful-curl (artful/curl/Dockerfile)
• artful-scm (artful/scm/Dockerfile)
• artful (artful/Dockerfile)
• buster-curl (buster/curl/Dockerfile)
• buster-scm (buster/scm/Dockerfile)
• buster (buster/Dockerfile)
• jessie-curl (jessie/curl/Dockerfile)
• jessie-scm (jessie/scm/Dockerfile)
• jessie (jessie/Dockerfile)
• sid-curl (sid/curl/Dockerfile)
• sid-scm (sid/scm/Dockerfile)
• sid (sid/Dockerfile)
• stretch-curl, curl (stretch/curl/Dockerfile)
• stretch-scm, scm (stretch/scm/Dockerfile)
• stretch, latest (stretch/Dockerfile)
• trusty-curl (trusty/curl/Dockerfile)
• trusty-scm (trusty/scm/Dockerfile)
• trusty (trusty/Dockerfile)
• wheezy-curl (wheezy/curl/Dockerfile)
• wheezy-scm (wheezy/scm/Dockerfile)
• wheezy (wheezy/Dockerfile)
• xenial-curl (xenial/curl/Dockerfile)
• xenial-scm (xenial/scm/Dockerfile)
• xenial (xenial/Dockerfile)
• zesty-curl (zesty/curl/Dockerfile)
• zesty-scm (zesty/scm/Dockerfile)
• zesty (zesty/Dockerfile)

Quick reference

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

• Where to file issues:
  https://github.com/docker-library/buildpack-deps/issues

• Maintained by:
  the Docker Community

• Supported architectures: (more info)
  amd64, arm32v5, arm32v7, arm64v8, i386, ppc64le, s390x

• Published image artifact details:
  repo-info repo’s repos/buildpack-deps/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/buildpack-deps
  official-images repo’s library/buildpack-deps file (history)

• Source of this description:
  docs repo’s buildpack-deps/ directory (history)

• Supported Docker versions:
  the latest release (down to 1.6 on a best-effort basis)

What is buildpack-deps?

In spirit, buildpack-deps is similar to Heroku’s stack images. It includes a large number of “development header” packages needed by various things like Ruby Gems, PyPI modules, etc. For example, buildpack-deps would let you do a bundle install in an arbitrary application directory without knowing beforehand that ssl.h is required to build a dependent module.

How to use this image

This stack is designed to be the foundation of a language-stack image.

What’s included?

The main tags of this image are the full batteries-included approach. With them, a majority of arbitrary gem install / npm install / pip install should be successful without additional header/development packages.

For some language stacks, that doesn’t make sense, particularly if linking to arbitrary external C libraries is much less common (as in Go and Java, for example), which is where these other smaller variants can come in handy.

curl

This variant includes just the curl, wget, and ca-certificates packages. This is perfect for cases like the Java JRE, where downloading JARs is very common and necessary, but checking out code isn’t.

scm

This variant is based on curl, but also adds various source control management tools. As of this writing, the current list of included tools is bzr, git, hg, and svn. Intentionally missing is cvs due to the dwindling relevance it has (sorry CVS). This image is perfect for cases like the Java JDK, where downloading JARs is very common (hence the curl base still), but checking out code also becomes more common as well (compared to the JRE).

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository’s buildpack-deps/ directory.

As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.