blob: ed51c8afd39db82edff58a9029189f7d1efbe1e3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
## Overall Docker Setup for Coq's CI.
This directory provides Docker images to be used by Coq's CI. The
images do support Docker autobuild on `hub.docker.com` and Gitlab's
private registry.
The Gitlab CI will build a Docker image unless the CI environment variable
`SKIP_DOCKER` is set to `true`. This image will be
stored in the [Gitlab container registry](https://gitlab.com/coq/coq/container_registry)
under the name given by the `CACHEKEY` variable from
the [Gitlab CI configuration file](../../../.gitlab-ci.yml).
`SKIP_DOCKER` is set to "true" in `https://gitlab.com/coq/coq` to avoid running
a lengthy redundant job. For efficiency, users should enable that setting
in forked repositories after the initial Docker build in the fork succeeds.
The steps to generate a new Docker image are:
- Update the `CACHEKEY` variable in .gitlab-ci.yml with the date and md5.
- Submit the change in a PR. This triggers a Gitlab CI run that
immediately fails, as the Docker image is missing and the `SKIP_DOCKER`
default value prevents rebuilding the image.
- Run a new pipeline on Gitlab with that PR branch (e.g. "pr-99999"), using the green
"Run pipeline" button on the [web interface](https://gitlab.com/coq/coq/pipelines),
with the `SKIP_DOCKER` environment variable set to `false`. This will run a
`docker-boot` process, and once completed, a new Docker image will be available in
the container registry, with the name set in `CACHEKEY`.
- Any pipeline with the same `CACHEKEY` will now automatically reuse that
image without rebuilding it from scratch.
In case you do not have the rights to run Gitlab CI pipelines, you should ask
the ci-maintainers Github team to do it for you.
## Manual Building
You can also manually build and push any image:
- Build the image `docker build -t base:$VERSION .`
To upload/push to your hub:
- Create a https://hub.docker.com account.
- Login into your space `docker login --username=$USER`
- Push the image:
+ `docker tag base:$VERSION $USER/base:$VERSION`
+ `docker push $USER/base:$VERSION`
## Debugging / Misc
To open a shell inside an image do `docker run -ti --entrypoint /bin/bash <imageID>`
Each `RUN` command creates an "layer", thus a Docker build is
incremental and it always help to put things updated more often at the
end.
## Possible Improvements:
- Use ARG for customizing versions, centralize variable setup;
|
