Building a container¶
Generally, building docker images inside of Gitlab CI is quite easy. The snippet below shows a very simple - but working - docker build inside of Gitlab CI. It includes logging in to Docker Hub, building and tagging the image as
appuio/docs-webserver:latest and pushing it to Docker Hub.
1 2 3 4 5 6 7 8 9
build: stage: deploy image: docker:latest services: - docker:dind script: - docker login -u $USERNAME -p $PASSWORD - docker build . -t appuio/docs-webserver:latest - docker push appuio/docs-webserver:latest
The most crucial part for this to work is the inclusion of
docker:dind as a service, as it provides the docker daemon that all the docker commands will use. The image we use to run the commands is simply the official docker image (it includes the docker binary).
$PASSWORD are Gitlab CI variables that are injected at runtime (it is generally bad practice to hardcode login details in a file inside a repository).
Gitlab CI doesn’t allow keeping the docker build cache (cached layers) as it is located outside the build context. There are various ways to circumvent this, but docker version 1.13 introduced a very nice new feature which helps in that regard.
As of 1.13, docker offers the possibility to take an existing image and use its layers as the cache for a new build. This can be achieved by pulling the image we would like to use as cache and using the flag
--cache-from when running
docker build. Pulling the image obviously costs some time, but it is nevertheless useful in many cases.
If we extend our snippet with these findings in mind, it would look as follows:
1 2 3 4 5 6 7 8 9 10
build: stage: deploy image: docker:latest services: - docker:dind script: - docker login -u $USERNAME -p $PASSWORD - docker pull appuio/docs-webserver:latest - docker build . --cache-from=appuio/docs-webserver -t appuio/docs-webserver - docker push appuio/docs-webserver:latest
This would already work for a successful deployment to APPUiO as the OpenShift platform can get its images directly from Docker Hub. However, if we want to take full advantage of Gitlab CI and the internal APPUiO registry, we will need some further configuration. More about this will be explained in one of the following sections.
Building (with) docker images inside of Gitlab CI generally requires some more preparations and system side configurations. We will assume that your Gitlab instance has already been correctly installed and configured, as system setup would be out of scope for this documentation.