gecko-dev/testing/docker
Wander Lairson Costa cf0a697064 Bug 1087456 part2: change builder image from "gecko-base" to "base". r=lightsofapollo,garndt
builder image is now based on the "base" image that lives on gecko
tree.

--HG--
extra : rebase_source : a22e083dca220a52e1b84cf5479969a6c1dc6882
extra : source : 664164ad527d89ce83812d15f99aaff656430f4b
2014-11-26 10:11:29 -08:00
..
base
builder Bug 1087456 part2: change builder image from "gecko-base" to "base". r=lightsofapollo,garndt 2014-11-26 10:11:29 -08:00
tester
build.sh
README.md
REGISTRY

Docker Images for Gecko

This folder contains various docker images used in taskcluster as well as other misc docker images which may be useful for hacking on gecko.

Building images

Generally images can pull from the registry rather then build locally but for developing new images its often helpful to hack on them locally.

# Example: ./build.sh base
./build.sh <FOLDER>

This is a tiny wrapper around building the docker images via docker build -t $REGISTRY/$FOLDER:$FOLDER_VERSION

Adding a new image

The docker image primitives are very basic building block for constructing an "image" but generally don't help much with tagging it for deployment so we have a wrapper (./build.sh) which adds some sugar to help with tagging/versioning... Each folder should look something like this:

  • your_amazing_image/
    • your_amazing_image/Dockerfile: Standard docker file syntax
    • your_amazing_image/VERSION: The version of the docker file (required* used during tagging)
    • your_amazing_image/REGISTRY: Override default registry (useful for secret registries)