Installing with Docker in Jenkins - Mechanics & Internals

Overview - Installing with Docker

What is it?

Installing Jenkins with Docker means running Jenkins inside a container. Docker is a tool that packages software and its environment together, so Jenkins can run anywhere without setup issues. This method simplifies installation by avoiding manual setup on your computer. It also makes Jenkins easy to update, move, or remove.

Why it matters

Without Docker, installing Jenkins can be complex and error-prone because it depends on many system settings and software versions. Docker solves this by isolating Jenkins in its own environment, making it reliable and consistent. This saves time and reduces frustration, especially when working on different machines or teams.

Where it fits

Before this, you should understand basic Docker concepts like containers and images. After learning this, you can explore configuring Jenkins pipelines, plugins, and scaling Jenkins with Docker in production.

Mental Model

Core Idea

Docker packages Jenkins and its environment into a container, so Jenkins runs the same way everywhere without manual setup.

Think of it like...

Installing Jenkins with Docker is like buying a fully assembled toy instead of building it yourself. The toy works right out of the box, no missing pieces or instructions needed.

┌───────────────┐
│   Host OS    │
│ ┌───────────┐ │
│ │  Docker   │ │
│ │ Container│ │
│ │  ┌─────┐ │ │
│ │  │Jenkins│ │ │
│ │  └─────┘ │ │
│ └───────────┘ │
└───────────────┘

Build-Up - 7 Steps

1

Foundation

Understanding Docker Containers

Concept: Learn what Docker containers are and how they isolate applications.

Docker containers are like lightweight boxes that hold an application and everything it needs to run. They share the computer's operating system but keep apps separate so they don't interfere with each other.

Result

You understand that Docker containers provide a consistent environment for apps like Jenkins.

Knowing containers isolate apps helps you see why Docker makes installing Jenkins easier and more reliable.

2

Foundation

What is Jenkins and Why Use It

Concept: Introduce Jenkins as a tool for automating software tasks.

Jenkins helps developers automatically build, test, and deliver software. It saves time by running these tasks without manual work.

Result

You know Jenkins is a software automation server that benefits from easy installation.

Understanding Jenkins' role shows why having it run smoothly with Docker is valuable.

3

Intermediate

Pulling the Official Jenkins Docker Image

🤔Before reading on: do you think the Jenkins image is built by the community or officially maintained? Commit to your answer.

Concept: Learn how to get the official Jenkins image from Docker Hub.

Run the command: docker pull jenkins/jenkins:lts This downloads the latest stable Jenkins image prepared by Jenkins maintainers.

Result

The Jenkins image is downloaded and ready to use on your machine.

Knowing to use the official image ensures you get a secure and tested Jenkins setup.

4

Intermediate

Running Jenkins Container with Port Mapping

🤔Before reading on: do you think Jenkins inside Docker can be accessed from your browser directly? Commit to your answer.

Concept: Learn how to start Jenkins in Docker and access it via a web browser.

Run: docker run -p 8080:8080 -p 50000:50000 jenkins/jenkins:lts This command starts Jenkins and maps its ports to your computer so you can open Jenkins at http://localhost:8080.

Result

Jenkins runs in a container and is accessible through your browser on port 8080.

Understanding port mapping connects the container's network to your computer, enabling interaction with Jenkins.

5

Intermediate

Persisting Jenkins Data with Volumes

🤔Before reading on: do you think Jenkins data inside the container is saved permanently by default? Commit to your answer.

Concept: Learn how to keep Jenkins data safe even if the container stops or is removed.

Run: docker run -p 8080:8080 -p 50000:50000 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts This creates a volume named jenkins_home to store Jenkins data outside the container.

Result

Jenkins data persists on your computer, surviving container restarts or removals.

Knowing how to use volumes prevents data loss and is essential for real Jenkins use.

6

Advanced

Customizing Jenkins with Dockerfile

🤔Before reading on: do you think you can add plugins or change Jenkins settings by editing the Docker image? Commit to your answer.

Concept: Learn how to create your own Jenkins Docker image with custom plugins or settings.

Create a Dockerfile: FROM jenkins/jenkins:lts RUN jenkins-plugin-cli --plugins git workflow-aggregator Build with: docker build -t myjenkins . Run your custom Jenkins with: docker run -p 8080:8080 myjenkins

Result

You have a Jenkins container with pre-installed plugins ready to use.

Custom images let you automate Jenkins setup, saving time and ensuring consistency.

7

Expert

Securing Jenkins Docker Installation

🤔Before reading on: do you think running Jenkins as root inside Docker is safe? Commit to your answer.

Concept: Learn best practices to run Jenkins securely in Docker containers.

Use the official Jenkins user by default (not root). Limit container permissions and use Docker networks to isolate Jenkins. Example: docker run -u 1000:1000 -p 8080:8080 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts Also, keep Jenkins and Docker updated regularly.

Result

Jenkins runs with limited permissions, reducing security risks.

Understanding security risks in containers helps protect your Jenkins server from attacks.

Under the Hood

Docker uses container technology to package Jenkins with its dependencies and environment. When you run the Jenkins Docker image, Docker creates a container with isolated filesystem, network, and process space. Jenkins runs inside this container as if on its own machine, but shares the host OS kernel. Volumes connect container storage to the host, preserving data outside the container lifecycle.

Why designed this way?

Docker was designed to solve the problem of software running differently on different machines. Packaging Jenkins in a container ensures it behaves the same everywhere. Using containers instead of full virtual machines makes it lightweight and fast. The official Jenkins image is maintained to provide a secure, stable base with common plugins and configurations.

Host OS
┌─────────────────────────────┐
│        Docker Engine         │
│ ┌───────────────┐           │
│ │ Jenkins Image │           │
│ │ ┌───────────┐ │           │
│ │ │ Jenkins   │ │           │
│ │ │ Server    │ │           │
│ │ └───────────┘ │           │
│ └───────────────┘           │
│ ┌───────────────┐           │
│ │ Volume (Data) │ <─────────┤
│ └───────────────┘           │
└─────────────────────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does running Jenkins in Docker mean Jenkins runs on a separate virtual machine? Commit yes or no.

Common Belief: Many think Docker containers are full virtual machines.

Reality: Docker containers share the host OS kernel and are much lighter than virtual machines.

Why it matters: Thinking containers are VMs leads to overestimating resource needs and misunderstanding performance.

Quick: If you delete a Jenkins Docker container, is your Jenkins data lost? Commit yes or no.

Common Belief: Some believe Jenkins data is safe inside the container by default.

Reality: Data inside containers is lost when containers are removed unless volumes are used.

Why it matters: Not using volumes causes data loss, meaning all Jenkins jobs and settings vanish unexpectedly.

Quick: Can you run Jenkins Docker container as root safely in production? Commit yes or no.

Common Belief: Running Jenkins as root inside Docker is safe and common.

Reality: Running as root increases security risks; best practice is to run Jenkins as a non-root user.

Why it matters: Ignoring this can expose your system to attacks if Jenkins or Docker is compromised.

Quick: Does pulling the 'latest' Jenkins Docker image always give you the most stable version? Commit yes or no.

Common Belief: Using 'latest' tag always means stable and recommended Jenkins version.

Reality: The 'latest' tag can be unstable; the 'lts' (long-term support) tag is recommended for stability.

Why it matters: Using unstable versions can cause unexpected failures in production Jenkins.

Expert Zone

1

The Jenkins Docker image uses a dedicated 'jenkins' user inside the container to improve security, but this user ID must be compatible with host permissions when mounting volumes.

2

Docker networking for Jenkins can be customized to isolate Jenkins from other containers or expose it securely, which is critical in multi-tenant environments.

3

Automating Jenkins Docker image builds with custom plugins and configurations ensures consistent environments across development, testing, and production.

When NOT to use

Using Docker for Jenkins is not ideal if you need deep integration with host hardware or very high performance, where native installation might be better. Also, for very simple or temporary Jenkins use, lightweight alternatives or cloud Jenkins services may be preferable.

Production Patterns

In production, Jenkins is often run in Docker with volumes for persistence, behind a reverse proxy for HTTPS, and integrated with orchestration tools like Kubernetes for scaling. Custom Docker images with pre-installed plugins and security hardening are standard practice.

Connections

Virtual Machines

Docker containers and virtual machines both isolate software but use different methods.

Understanding the difference helps choose the right isolation tool for Jenkins deployment.

Continuous Integration/Continuous Delivery (CI/CD)

Jenkins installed with Docker is a key enabler for CI/CD pipelines.

Knowing how Jenkins runs in Docker helps build reliable automated software delivery systems.

Shipping and Logistics

Docker containers are like shipping containers that standardize transport of goods.

This cross-domain view clarifies why Docker ensures Jenkins runs consistently anywhere.

Common Pitfalls

#1 Not using volumes causes Jenkins data loss when containers are removed.

Wrong approach:

docker run -p 8080:8080 jenkins/jenkins:lts

Correct approach:

docker run -p 8080:8080 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts

Root cause:

Misunderstanding that container storage is temporary and isolated from the host.

#2 Running Jenkins container as root user increases security risks.

Wrong approach:

docker run -p 8080:8080 --user root jenkins/jenkins:lts

Correct approach:

docker run -p 8080:8080 jenkins/jenkins:lts

Root cause:

Ignoring the default non-root user in the Jenkins image and Docker security best practices.

#3 Using 'latest' tag for Jenkins image in production can cause instability.

Wrong approach:

docker pull jenkins/jenkins:latest

Correct approach:

docker pull jenkins/jenkins:lts

Root cause:

Assuming 'latest' means stable without checking Jenkins release policies.

Key Takeaways

Docker containers package Jenkins with all its dependencies, making installation simple and consistent across machines.

Using official Jenkins Docker images and volumes ensures security and data persistence.

Port mapping connects Jenkins inside Docker to your computer, allowing easy access via a browser.

Custom Dockerfiles let you automate Jenkins setup with plugins and configurations for repeatable environments.

Security best practices like running Jenkins as a non-root user inside Docker protect your system from vulnerabilities.