{"id":7359,"date":"2021-06-22T16:32:11","date_gmt":"2021-06-22T16:32:11","guid":{"rendered":"https:\/\/linuxways.net\/?p=7359"},"modified":"2021-06-22T16:32:11","modified_gmt":"2021-06-22T16:32:11","slug":"install-and-run-jenkins-with-systemd-and-docker","status":"publish","type":"post","link":"https:\/\/linuxways.net\/de\/ubuntu\/install-and-run-jenkins-with-systemd-and-docker\/","title":{"rendered":"Install and Run Jenkins with Systemd and Docker"},"content":{"rendered":"

When you download and configure Jenkins using docker, you have to use manual command to manage the process. It becomes quite unsafe and complicated. So, we will manage it using systemd. Actually, it is the system and service manager for Linux operating systems. It features on-demand starting, enabling, restarting, and stopping of daemons, logging, etc.<\/p>\n

In this article, I am going to download the Jenkins package from docker hub repository and manage it using systemd manager. I have used Ubuntu Linux, but you can do it in centos, Debian, Redhat etc which support systemd.<\/p>\n

Prerequisites<\/h2>\n
    \n
  1. Latest version of docker installed<\/li>\n
  2. Internet connection for downloading Jenkins image<\/li>\n<\/ol>\n

    Configuration<\/h2>\n

    To run a process we need users. So, we create a system group, add a system user to the group. As you don\u2019t need to login we provide no login shell. I have here given the name \u2018devops\u2019, you can give of your choice.<\/p>\n

    $ sudo groupadd --system devops<\/pre>\n
    $ sudo useradd -s \/sbin\/nologin --system -g devops devops<\/pre>\n
    During docker installation, a user docker was added by default. So to run our process inside docker, let\u2019s add \u2018devops\u2019 user and your current login user to the docker group.<\/p>\n
    $ sudo usermod -aG docker devops<\/pre>\n
    $ sudo usermod -aG docker $USER<\/pre>\n
    We need a directory to map container volume to the host. So, let\u2019s create a directory and give current user ownership in the directory.<\/p>\n
    $ sudo mkdir -p \/data\/jenkins<\/pre>\n
    $ chown -R $USER:$USER \/data\/jenkins<\/pre>\n
    You can now verify user \u2018devops\u2019 using the following command. Your output must be similar to the following.<\/p>\n
    $ id devops<\/pre>\n
    <\/p>\n
    Now it\u2019s time to create a service. The service files are stored inside \/etc\/systemd\/system\/ So, create a file ending with .service as shown below.<\/p>\n
    $ vim \/etc\/systemd\/system\/docker-jenkins.service<\/pre>\n
    Add following content in the file. The following configuration will create a service name docker-jenkins. It will simply pull the latest version of jenkins image from docker hub and run the container. It will also map port 8080 and 50000 in the host server, which are needed to access jenkins service. As defined in the Unit section below, it requires docker.service to be executed successfully. If you have different users, mount points change accordingly.<\/p>\n
    [Unit]\r\n\r\nDescription=My Jenkins Server\r\n\r\nDocumentation=https:\/\/jenkins.io\/doc\/\r\n\r\nAfter=docker.service\r\n\r\nRequires=docker.service\r\n\r\n[Service]\r\n\r\nType=simple\r\n\r\nUser=devops\r\n\r\nGroup=devops\r\n\r\nTimeoutStartSec=0\r\n\r\nRestart=on-failure\r\n\r\nRestartSec=30s\r\n\r\nExecStartPre=-\/usr\/bin\/docker kill jenkins-server\r\n\r\nExecStartPre=-\/usr\/bin\/docker rm jenkins-server\r\n\r\nExecStartPre=\/usr\/bin\/docker pull jenkins\/jenkins\r\n\r\nExecStart=\/usr\/bin\/docker run \\\r\n\r\n--name jenkins-server \\\r\n\r\n--publish 8080:8080 \\\r\n\r\n--publish 50000:50000 \\\r\n\r\n--volume \/data\/jenkins:\/var\/jenkins_home \\\r\n\r\njenkins\/jenkins\r\n\r\nSyslogIdentifier=jenkin\r\n\r\nExecStop=\/usr\/bin\/docker stop jenkins-server\r\n\r\n[Install]\r\n\r\nWantedBy=multi-user.target<\/pre>\n
    Reload the service file in the systemd daemon, using the following command.<\/p>\n
    $ sudo systemctl daemon-reload<\/pre>\n
    Start the docker service using the command below.<\/p>\n
    $ sudo systemctl start docker-jenkins<\/pre>\n
    <\/p>\n
    Systemd also provides default logging service in syslog. You can see the log in the following location.<\/p>\n
    $ sudo tail -f \/var\/log\/syslog<\/pre>\n
    Now, you can start the service after the server reboots using the \u2018enabling\u2019 feature of systemd manager.<\/p>\n
    $ sudo systemctl enable docker-jenkins<\/pre>\n
    Also, check by restarting the service.<\/p>\n
    $ sudo systemctl restart docker-jenkins<\/pre>\n
    Jenkins setup<\/h2>\n
    To setup jenkins first visit http:\/\/yourserverip:8080<\/a> Then you need to enter the initial admin password, which is set in the following path. Copy the output and paste it in \u201cAdministrator password\u2019. Then click on continue.<\/p>\n
    $ cat \/data\/jenkins\/secrets\/initialAdminPassword<\/pre>\n
    <\/p>\n
    You can install the required plugin and continue.<\/p>\n
    <\/p>\n
    Conclusion<\/h2>\n
    In this article, you learnt how to install the latest version of Jenkins using docker and configure the service to use it. Managing Jenkins with systemd makes the work simpler. Thank you for reading.<\/p>","protected":false},"excerpt":{"rendered":"
    When you download and configure Jenkins using docker, you have to use manual command to manage the process. It becomes quite unsafe and complicated. So, we will manage…<\/p>","protected":false},"author":1,"featured_media":7556,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[160,248,100],"class_list":["post-7359","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ubuntu","tag-docker","tag-jenkins","tag-ubuntu-20-04"],"_links":{"self":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/7359","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/comments?post=7359"}],"version-history":[{"count":0,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/7359\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media\/7556"}],"wp:attachment":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media?parent=7359"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/categories?post=7359"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/tags?post=7359"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}