armel organization is deprecated in favor of the more-specific
arm32v5 organization, as per https://github.com/docker-library/official-images#architectures-other-than-amd64. Please adjust your usages accordingly.
Supported tags and respective
THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289 IS STILL IN-PROGRESS (which is the first step towards proper multiarch images)
PLEASE DO NOT USE THEM FOR IMPORTANT THINGS
This image is built from the source of the official image of the same name (
buildpack-deps). Please see that image's description for links to the relevant
If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the
tianon/jenkins-groovy GitHub repository, which are responsible for creating the Jenkins jobs which build them.
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
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.
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.
This variant includes just the
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.
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
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).
View license information for the software contained in this image.