mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-01 06:35:42 +00:00
71cd0fcbd1
--HG-- extra : rebase_source : f59ae0290f04feaafefe893efa0d0da2eb635747 extra : source : deadeba968b58c4ee1fedb39854444938a27e8e9
41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
# Docker Images for Gecko
|
|
|
|
This folder contains various docker images used in [taskcluster](http://docs.taskcluster.net/) as well as other misc docker images which may be useful for
|
|
hacking on gecko.
|
|
|
|
## Building images
|
|
|
|
Generally images can pull from the [registry](./REGISTRY) rather then
|
|
build locally but for developing new images its often helpful to hack on
|
|
them locally.
|
|
|
|
```sh
|
|
# 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)
|
|
|
|
## Conventions
|
|
|
|
In some image folders you will see `.env` files these can be used in
|
|
conjunction with the `--env-file` flag in docker to provide a
|
|
environment with the given environment variables. These are primarily
|
|
for convenience when manually hacking on the images.
|