{"id":3214,"date":"2021-10-07T13:09:09","date_gmt":"2021-10-07T12:09:09","guid":{"rendered":"https:\/\/inlab.fib.upc.edu\/?p=3214"},"modified":"2023-05-24T09:18:05","modified_gmt":"2023-05-24T08:18:05","slug":"runners-2","status":"publish","type":"post","link":"https:\/\/inlab.fib.upc.edu\/en\/news\/runners-2","title":{"rendered":"Runners"},"content":{"rendered":"

Gitlab CI\/CD<\/strong> is a DevOps tool integrated into Gitlab to be able to make continuous integration, continuous delivery and continuous deployment. In order to use this tool you must use the Gitlab Runners, which are applications that are responsible for running the Gitlab CI\/CD pipeline jobs.<\/p>\n

Although Gitlab servers may have shared runners that any user can use, we may be interested in having one or more Runners in our machine. In this article we will explain how you can do it quickly and easily.<\/p>\n

Installation using Docker containers<\/strong><\/h2>\n

There are multiple ways to install a Runner on a machine, but the most flexible way and the one we will explain in this article is using Docker containers<\/p>\n

The requirements to be able to install and use a Runner with Docker are as follows:<\/p>\n

    \n
  • Have a machine with Docker installed and understand its basic operation <\/li>\n
  • Have a Runners registration token<\/strong> in a Gitlab group or project<\/li>\n<\/ul>\n

    To obtain the registration token you only have to go to the group or project where we want to register the Runner and access “Settings -> CI\/CD -> Runners<\/strong>“.<\/p>\n

    It is important that you keep the token<\/strong> secret, since using this token anyone can register a Runner in your project and potentially gain access to the files. If you leak it, press the “Reset registration token<\/strong>” button to get a new one.<\/p>\n

                                                               \"\"<\/p>\n

    Un cop obtingut el token de registre cal crear el contenidor que s\u2019encarregar\u00e0 d\u2019executar els Runners. Per fer-ho cal executar les seg\u00fcents comandes amb permisos d\u2019administrador:<\/p>\n

    Once the registration token is obtained, you must create the container that will be in charge of running the Runners. To do this, you must execute the following orders with <\/span>
    \nadministrator permissions:<\/span><\/p>\n

    \r\ndocker volume create gitlab-runner-config\r\ndocker run -d --name gitlab-runner --restart always \\\r\n    -v \/var\/run\/docker.sock:\/var\/run\/docker.sock \\\r\n    -v gitlab-runner-config:\/etc\/gitlab-runner \\\r\n    gitlab\/gitlab-runner:latest\r\n<\/pre>\n
                                                      \"\"                                                         <\/p>\n
    The next step is to register a Runner to run our pipelines. This can be done by running the following order and supplying the data it requests:                                                                                                             <\/p>\n
    \r\ndocker run --rm -it -v gitlab-runner-config:\/etc\/gitlab-runner <\/span><\/pre>\n
    \r\ngitlab\/gitlab-runner:latest register \r\n<\/pre>\n
                                                   \"\"                                               <\/p>\n
    Finally, you have to go to Settings<\/strong>, CI\/CD<\/strong>, Runners<\/strong> and see if the Runner appears in the “Available specific runners<\/strong>” section.                                                                                             <\/p>\n
                                                                         \"\"<\/p>\n
    If it appears it is that everything has gone well and we can already use it to run our pipelines. In case it is necessary to have more Runners, just repeat the order used to register a new one.                                   <\/p>\n
     <\/p>\n","protected":false},"excerpt":{"rendered":"
    Gitlab CI\/CD is a DevOps tool integrated into Gitlab to be able to make continuous integration, continuous delivery and continuous deployment. In order to use this tool you must use the Gitlab Runners, which are applications that are responsible for running the Gitlab CI\/CD pipeline jobs. Although Gitlab servers may have shared runners that any […]<\/p>\n","protected":false},"author":1211,"featured_media":3171,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[571],"tags":[],"experteses":[],"class_list":["post-3214","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"_links":{"self":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/3214","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/users\/1211"}],"replies":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/comments?post=3214"}],"version-history":[{"count":1,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/3214\/revisions"}],"predecessor-version":[{"id":20823,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/3214\/revisions\/20823"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/media\/3171"}],"wp:attachment":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/media?parent=3214"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/categories?post=3214"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/tags?post=3214"},{"taxonomy":"experteses","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/experteses?post=3214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}