7

I still don't quite understand the process for a gitlab-ci multi runner to start a docker and interact inside with the code.

Is it possible for a gitlab-ci multi runner to start a docker container having the current code inside this docker container and then run tests against this code? (e.g.: code linting)

I basically want a docker container that has various linters installed. GitLab-CI multi runner should run on the host system and start the docker container on-demand. Inside the docker container, the code should be checked against phpcs for example.

How do I get the repo code into the docker container?

Thanks for the help

Improve this question
0

3 Answers 3

Reset to default
1

First, gitlab-runner needs to have the Docker socket mounted as described in the documentation:

docker run -d --name gitlab-runner --restart always \
 -v /var/run/docker.sock:/var/run/docker.sock \
 -v /srv/gitlab-runner/config:/etc/gitlab-runner \
 gitlab/gitlab-runner:latest

Afterwards, you have to register the runner with:

  1. docker as executor.
  2. the Docker image with the linters you want as Docker image.
Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

Every docker client will forward the commands to the docker daemon,the docker daemon will listen to the local port such as http,tcp or unix socket.

When you start container like this:

docker run -d --name gitlab-runner --restart always \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /srv/gitlab-runner/config:/etc/gitlab-runner \ gitlab/gitlab-runner:latest

All the docker commands will forward to the host,as the docker was listening on unix:///var/run/docker.sock

PS: You nedd to install docker in the gitlab-runnercontainer

Improve this answer

Comments

0

I know this question is old, but I thought I answer it anyway, since I've been working on similar things at the moment and I thought I would like to answer it in a larger scale, to give a basic idea, a starting point, understanding the build process with GitLab-CI.

There are different ways to install a gitlab-runner on a system, as described here. It always will get down to installing the runner and after that registering the runner at your gitlab instance.

You will be guided through the registering process here. During the registering process you will have to choose the executor on which builds will be realized. These can be ssh, docker+machine, docker-ssh+machine, kubernetes, docker, parallels, virtualbox, docker-ssh and shell: docker.

Suppose you choose docker as an executor. Once a build has been passed to your runner, it will start a build container in which the build will be executed. In some project setups is no image defined as a 'base environment'. So during the (docker executor) runner registration you will be asked to define a default image that can be used as the build container, the environment for your build.

So if you have a project that is not defining a 'base environment' you have to choose one fulfilling your builds needs. E.g. if you run your build defined in an ant script you will either need an image that has ant installed or you will need to set up ant in your .gitlab-ci.yml.

In the .gitlab-ci.yml you will describe your build pipeline(s) (see more about that here). There you also can define more precisely how to clone your repo into your build container. But with the default configuration the cloning will happen every time a contributor is pushing changes on your code base to the git(lab) repository.

GitLab requires you to use the built-in git repository. This enables GitLab to clone the repos without further configuration (besides the administrative configuration you will have to go through setting up GitLab and maintaining it).

You can support the build container with additional containers (called 'services'), e.g. a database container for the tests to be run against during the build process.

For further information also see https://docs.gitlab.com/runner/ and https://docs.gitlab.com/ee/README.html

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.