Also, importantly, you’ll want to disable any shared or group runners for those repositories so that they end up actually using this privileged runner. So, for example, it would probably be advisable to assign specific repositories to the runner rather than entire groups. ? If you do add a runner using the -docker-privileged then you’ll probably want to be selective about what repositories have access to that runner. If you refresh the Settings > CI/CD page you should see the newly created runner listed. However, you can restart manually just to be sure: docker restart gitlab-runner
The runner should be automatically restarted.
#DOCKER RUN IMAGE INSTALLED ELSEWHERE INSTALL#
I’m going to install GitLab Runner as a Docker service on an underutilised EC2 instance.īackground information on Continuous Integration with GitLab can be found here.
However, the total time constraint has become a serious limitation (ideally I want to rebuild my project fairly regularly). I’ve been using the shared runners on GitLab. I’ve got a project which takes a long time to build.