docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
docs/buildpack-deps
History
Tianon Gravi b99c182504 Add a sentence with a link to the manifest file for reach repo 2014-10-16 15:28:31 -06:00
..
.keep adding some directories for andrew to dump the short and long desc in 2014-07-31 15:09:43 -06:00
README-short.txt Update a number of short descriptions to be 100 characters or less to reflect the new Hub length restriction 2014-10-08 16:42:40 -06:00
README.md Add a sentence with a link to the manifest file for reach repo 2014-10-16 15:28:31 -06:00
content.md Add LOGO magic to many contents and update.sh 2014-09-26 17:22:36 -06:00
license.md Rename LICENSE -> license 2014-09-22 21:38:41 -06:00
logo.png logos for all the things 2014-08-06 16:37:56 -06:00

README.md

Supported tags and respective Dockerfile links

For more information about this image and its history, please see the relevant manifest file (library/buildpack-deps) in the docker-library/official-images GitHub repo.

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.

logo

How to use this image

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

License

View license information for the software contained in this image.

User Feedback

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

Contributing

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.