- #HOW TO REMOVE GECKO DRIVER CACHE IN CONTAINER HOW TO#
- #HOW TO REMOVE GECKO DRIVER CACHE IN CONTAINER INSTALL#
( docker and docker-compose) and run the job script in context of that The second approach is to use the special docker-in-docker (dind)
#HOW TO REMOVE GECKO DRIVER CACHE IN CONTAINER INSTALL#
You can now use docker command and install docker-compose if needed. docker run my-docker-image /script/to/run/tests gitlab-ci.yml: before_script : - docker info build_image : script : - docker build -t my-docker-image. You can now verify that everything works by adding docker info to. Verify that gitlab-runner has access to Docker: sudo -u gitlab-runner -H docker info
#HOW TO REMOVE GECKO DRIVER CACHE IN CONTAINER HOW TO#
GitLab Runner then executes job scripts as the gitlab-runner user.ĭuring GitLab Runner installation select shell as method of executing job scripts or use command: sudo gitlab-runner register -n \ -url \ -registration-token REGISTRATION_TOKEN \ -executor shell \ -description "My Runner"įor more information how to install Docker Engine on different systemsĪdd gitlab-runner user to docker group: sudo usermod -aG docker gitlab-runner The simplest approach is to install GitLab Runner in shell execution mode. There are three methods to enable the use of docker build and docker run during jobs each with their own tradeoffs. This requires special configuration of GitLab Runner to enable docker support during jobs. It's also useful when your application already has the Dockerfile that can be used to create and test an image: $ docker build -t my-image dockerfiles/ $ docker run my-docker-image /script/to/run/tests $ docker tag my-image my-registry:5000/my-image $ docker push my-registry:5000/my-image