|
|
11 years ago | |
|---|---|---|
| library | 11 years ago | |
| stackbrew | 11 years ago | |
| .gitignore | 12 years ago | |
| README.md | 11 years ago |
Stackbrew is a web-application that performs continuous building of the docker
standard library. See README.md in the stackbrew subfolder for more
information.
The library definition files are plain text files found in the library/
subfolder of the stackbrew repository.
The name of a definition file will determine the name of the image(s) it
creates. For example, the library/ubuntu file will create images in the
<namespace>/ubuntu repository. If multiple instructions are present in
a single file, all images are expected to be created under a different tag.
Note: there is no backwards compatibility with the old format. This is part of our effort to create strict, unambiguous references to build images upon.
<docker-tag>: <git-url>@<git-tag>
2.4.0: git://github.com/dotcloud/[email protected]
<docker-tag>: <git-url>@<git-commit-id>
2.2.0: git://github.com/dotcloud/docker-redis@a4bf8923ee4ec566d3ddc212
<docker-tag>: <git-url>@<git-tag-or-commit-id> <dockerfile-dir>
2.5.1: git://github.com/dotcloud/[email protected] tools/dockerfiles/2.5.1
Stackbrew will fetch data from the provided git repository from the
provided reference. Generated image will be tagged as <docker-tag>.
If a git tag is removed and added to another commit,
you should not expect the image to be rebuilt. Create a new tag and submit
a pull request instead.
Optionally, if <dockerfile-dir> is present, stackbrew will look for the
Dockerfile inside the specified subdirectory instead of at the root.
Thank you for your interest in the stackbrew project! We strive to make these instructions as simple and straightforward as possible, but if you find yourself lost, don't hesitate to seek us out on IRC freenode, channel #docker or by creating a github issue.
# maintainer: Your Name <[email protected]> (@github.name)@ symbol (found in the relevant MAINTAINERS file).