jessie-curl,curl(jessie/curl/Dockerfile)jessie-scm,scm(jessie/scm/Dockerfile)jessie,latest(jessie/Dockerfile)precise-curl(precise/curl/Dockerfile)precise-scm(precise/scm/Dockerfile)precise(precise/Dockerfile)sid-curl(sid/curl/Dockerfile)sid-scm(sid/scm/Dockerfile)sid(sid/Dockerfile)stretch-curl(stretch/curl/Dockerfile)stretch-scm(stretch/scm/Dockerfile)stretch(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)wily-curl(wily/curl/Dockerfile)wily-scm(wily/scm/Dockerfile)wily(wily/Dockerfile)xenial-curl(xenial/curl/Dockerfile)xenial-scm(xenial/scm/Dockerfile)xenial(xenial/Dockerfile)
For more information about this image and its history, please see the relevant manifest file (library/buildpack-deps). This image is updated via pull requests to the docker-library/official-images GitHub repo.
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the buildpack-deps/tag-details.md file in the docker-library/docs GitHub repo.
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.
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 successfull 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 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.
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).
View license information for the software contained in this image.
This image is officially supported on Docker version 1.11.1.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
Documentation for this image is stored in the buildpack-deps/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.
You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.