Image for post
Image for post

Run Jenkins in a Docker container — part 3 — run as root user

Guide for developers to get up and running with Jenkins running in Docker (on Windows).

This small series of guides will walk through three solutions for installing Jenkins in a Docker container on Windows, along with the configuration necessary to spin up dynamic build slaves also using Docker containers.

Running locally on a personal device is perfect for individual users, freelancers, or developers looking to do local Jenkinsfile or Shared Library development and testing before pushing to a central CI/CD platform.

“You said three solutions?” Yes — this article demonstrates running the Jenkins container as root user instead of jenkins user. Part 1 was using Docker-in-Docker and Part 2 was to replace with a socat container. Read both of those articles below or scroll to continue with the final article in the series.

What was wrong with using Docker-in-Docker

This article discusses the pros and cons of Docker-in-Docker and argues against using it for CI systems like Jenkins.

It suggests a better pattern would be to provide the container access to the host daemon directly via sharing a volume for its unix socket /var/run/docker.sock— and this is possible on Windows too since we are using WSL — the primary obstacle we face is that the jenkins user doesn’t have the required permissions.

Further complexity follows as the jenkins user obviously doesn’t exist on the Windows host, only within the context of the Jenkins container — which rules out using usermod -AG docker jenkins. The command has zero effect.

And the setfacl approach to give the ‘jenkins’ user read-write access to /var/run/docker.sock works —yay! — but doesn’t persist between restarts of Docker daemon on the host Windows machine.

So to conclude — this article will set up Jenkins to run as root user and map the /var/run/docker.sock into the container. If you balk at the thought of running as root, even locally, please check out parts 1 and 2 of this series.

Running Jenkins container as root

The steps we will go through;

  1. Command line, step-by-step to set up Jenkins.
  2. Configure Jenkins via the Console UI and set up the “docker” plugin.
  3. Verify the set up via a couple of test jobs.
  4. Translate the command lines into a Docker Compose template.


We assume you have Docker installed — for this demo I am running on a Windows 10 laptop with WSL enabled (Hyper-V is also okay).


Before we start up, create a volume that you will use for your Jenkins home directory — that way it will persist between restarts.

docker volume create jenkins-data


We’re going to use a bridge network called jenkins which we create by running the command docker network create jenkins. In the rest of our configuration, we will attach our container to this network.

Running Jenkins

We’re going to use the jenkinsci/blueocean image that comes pre-built with Blue Ocean.

We will map /var/run/docker.sock to allow our container access to the Docker host, and important we specify -u root so that we can talk to the socket without additional configuration.

docker container run --name jenkins-blueocean \
--detach --restart unless-stopped \
--network jenkins \
--user root \
--volume jenkins-data:/var/jenkins_home \
--volume /var/run/docker.sock:/var/run/docker.sock \
--publish 8080:8080 --publish 50000:50000 \

Now that Jenkins is started, head over to http://localhost:8080 to go through the initial set up wizard.

Jenkins Set Up Wizard

We won’t go through the Jenkins set up wizard in any detail — the important thing to note however is how to access your admin user unlock code, which you can find this from your running container via the following command:

docker exec jenkins-blueocean cat /var/jenkins_home/secrets/initialAdminPassword

Configuring Docker Cloud

Once you have your Jenkins set up complete, we need to set up running our Jenkins slaves as Docker containers. Head over to “Manage Plugins” and install the docker plugin.

Image for post
Image for post

Once installed, go to Manage Nodes and Clouds and then Configure Clouds and Add a new cloud. The type of “docker” should automatically appear in the dropdown.

You want to set the Docker Host URI to unix:///var/run/docker.sock and then run a Test Connection.

Image for post
Image for post

This is great — now we can reach the Docker daemon.

Configuring Docker Slaves/Agents

Next step is to set up an agent to run our pipelines against. Once you start developing, you can start building your own build containers and attaching these instead. For now, we shall use the jenkins/agent image.

Relevant fields below include giving it a label and name. The label allows you to associate a job to a particular agent — so you can always run a Maven build on an Agent that has maven installed, for example.

Image for post
Image for post

Our Connect Method will be Attach Docker Container. This runs the Docker container on the host machine.

Save everything and we are now ready to create a test job.

Verifying it all works

You are now ready to create a job to check that all is set up and working correctly. Create a new freestyle job. I’ve called mine “test-agent”.

You want to select the agent that this job will run on.

Image for post
Image for post

Down under build, write a simple “hello world” message as a test.

Image for post
Image for post

Save and build your new job. Jenkins will download the image for your container and run the job upon it. On completion you should get output such as that shown below.

Image for post
Image for post

All done. Success!

Docker Compose

Command line is all well and good, but it’s much easier to define as a docker compose yaml file. Start up with docker-compose up -d.

version: '3.8'networks:
name: jenkins
name: jenkins-data
services: jenkins:
container_name: jenkins-blueocean
image: jenkinsci/blueocean
restart: unless-stopped
user: root
- jenkins-network
- 8080:8080
- 50000:50000
- data:/var/jenkins_home
- /var/run/docker.sock:/var/run/docker.sock

A note from the author

Thank you for reading this article and I hope you found time to read the original part 1 and could contrast against the solution in part 2 as well — I hope you found them useful and via one of the articles you settled on a technique that suited your personal set up.

All source code for these articles can be found on GitHub.

You can follow me on Twitter and connect on LinkedIn.

Written by

DevOps | SRE | AWS | GCP

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store