Jenkins with access to hosts Docker engine
This tutorial provider Docker Compose configuration for running Jenkins inside a container with Docker client that controls host machines Docker engine using a socket. This works well in development environments as you can inspect containers created by Jenkins from the host system.
Note that by default each of the example Docker Compose configurations will create their own volumes for the data. This might not be what you want, if you want to use configuration from Integrating Jenkins and SonarQube as well. In order to use the same volumes for every docker compose configuration, run docker compose with -p (or --project-name) option. This can also be done by setting COMPOSE_PROJECT_NAME environment variable:
Jenkins image with Docker client
To be able run Docker commands from inside the Jenkins container, we will need to install the Docker client. This can be done with a suitable Dockerfile:
FROM jenkins/jenkins:lts-alpine
# Change user to root in order to have permissions to install packages.
USER root
# Only Docker client is required inside the Jenkins container as the host
# systems Docker engine is used from inside the container.
RUN apk add docker-cli
# Note that the user is not switched back to jenkins here. This is to avoid
# problems with docker socket permissions. Do not use root user in production.
# Instead, match group IDs of docker groups in host and container and add
# jenkins user to the docker group.
Jenkins container with access to hosts Docker engine
When running Jenkins in a container, we will want to define ports and volumes. To do this, we will use a docker-compose.yml configuration:
services:
jenkins:
build: .
ports:
# Web user interface
- 8080:8080
# Java agents
- 50000:50000
volumes:
# Persistent volume for the Jenkins data
- "jenkins.data:/var/jenkins_home"
# Host systems docker socket
- "/var/run/docker.sock:/var/run/docker.sock"
volumes:
jenkins.data:
These files are available in the repository that provides this website. In order to run Jenkins container with Docker-in-Docker support, cd into docs/tutorials/jenkins/jenkins-host-docker directory and run docker compose up.
To run the Jenkins container in the background, execute docker compose up command with -d/--detach flag:
This allows the Jenkins container to continue running even if you close the terminal session. Use docker compose logs command to see the logs.
To run the Jenkins container in the foreground, execute docker compose up command without -d/--detach flag:
You can now monitor the logs produced by the Jenkins container in your current shell. However, if you close the terminal session or send an interrupt signal (for example by pressing CTRL+C), the Jenkins container will be stopped.
The initial admin password can be printed with docker compose exec command:
In order to get started with Jenkins, the suggested plugins are often good a starting point. If you are planning to create pipeline projects with stages running in on-demand Docker containers, you will also need Docker Pipeline plugin. This can be installed through the Manage Jenkins > Manage plugins menu.