Installing with Docker in Jenkins - Visual Walkthrough

Process Flow - Installing with Docker

Pull Jenkins Docker Image

↓

Run Jenkins Container

↓

Container Starts Jenkins Service

↓

Access Jenkins via Browser

↓

Complete Initial Setup

This flow shows the steps to install Jenkins using Docker: pulling the image, running the container, starting Jenkins, accessing it, and finishing setup.

Execution Sample

Jenkins

docker pull jenkins/jenkins:lts

docker run -d -p 8080:8080 -p 50000:50000 --name jenkins jenkins/jenkins:lts

Pulls the official Jenkins LTS Docker image and runs it as a container exposing ports for web and agent communication.

Process Table

Step	Command	Action	Result
1	docker pull jenkins/jenkins:lts	Download Jenkins image from Docker Hub	Image downloaded locally
2	docker run -d -p 8080:8080 -p 50000:50000 --name jenkins jenkins/jenkins:lts	Start Jenkins container in detached mode	Container running, Jenkins service started
3	Access http://localhost:8080	Open Jenkins web interface in browser	Jenkins setup page loads
4	Complete initial setup wizard	Configure Jenkins admin user and plugins	Jenkins ready to use

💡 Setup completes after finishing the initial configuration wizard in the browser.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Jenkins Image	Not present	Downloaded locally	Available for container	Available	Available
Jenkins Container	Not running	Not running	Running	Running	Running
Jenkins Service	Stopped	Stopped	Started inside container	Started	Started
Browser Access	No	No	No	Yes	Yes

Key Moments - 3 Insights

Why do we need to map ports 8080 and 50000 when running the Jenkins container?

Port 8080 is for accessing Jenkins web interface in the browser, and port 50000 is for Jenkins agents to communicate. Without mapping, these services won't be reachable outside the container (see execution_table step 2).

What does the '-d' flag do in the docker run command?

The '-d' flag runs the container in detached mode, meaning it runs in the background so your terminal is free for other commands (see execution_table step 2).

Why do we need to complete the initial setup in the browser?

Jenkins requires initial configuration like setting up an admin user and installing plugins before it can be used (see execution_table step 4).

Visual Quiz - 3 Questions

Look at the execution table, what happens immediately after running the docker run command?

A Jenkins container starts and service runs

B Jenkins setup page loads in the browser

C Jenkins image is downloaded

D Initial setup wizard is completed

💡 Hint

Check step 2 in the execution_table for what docker run does.

At which step do you first access Jenkins through the browser?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Action' column in execution_table to find when browser access happens.

If you omit the port mapping '-p 8080:8080' in the docker run command, what will happen?

A Jenkins will still be accessible on port 8080

B Jenkins container will fail to start

C You won't be able to access Jenkins web interface from your browser

D Jenkins will use a random port automatically

💡 Hint

Refer to variable_tracker for Browser Access and port mapping importance.

Concept Snapshot

Install Jenkins with Docker:
1. Pull image: docker pull jenkins/jenkins:lts
2. Run container: docker run -d -p 8080:8080 -p 50000:50000 --name jenkins jenkins/jenkins:lts
3. Access Jenkins at http://localhost:8080
4. Complete setup wizard
Ports 8080 and 50000 must be mapped for web UI and agent communication.

Full Transcript

To install Jenkins using Docker, first pull the official Jenkins LTS image with 'docker pull jenkins/jenkins:lts'. Then run it as a container in detached mode with ports 8080 and 50000 mapped using 'docker run -d -p 8080:8080 -p 50000:50000 --name jenkins jenkins/jenkins:lts'. This starts Jenkins inside the container. Next, open a browser and go to http://localhost:8080 to access the Jenkins web interface. Finally, complete the initial setup wizard to configure Jenkins for use. Mapping ports is essential to access Jenkins and allow agent communication. The '-d' flag runs the container in the background so your terminal stays free. The process ends after finishing the setup wizard in the browser.

Practice

1. What is the main advantage of installing Jenkins using Docker?

easy

A. It only works on Windows systems

B. It requires manual setup of all dependencies

C. It disables Jenkins security features

D. It makes Jenkins installation quick and clean

Solution

1. Step 1: Understand Docker's role in Jenkins installation

   Docker packages Jenkins and its dependencies in a container, simplifying setup.

2. Step 2: Identify the benefit of containerization

   This containerization makes installation fast and keeps the system clean without leftover files.

3. Final Answer:

   It makes Jenkins installation quick and clean -> Option D

4. Quick Check:

   Docker simplifies Jenkins install = A [OK]

Hint: Docker containers isolate Jenkins for easy setup [OK]

Common Mistakes:

• Thinking Docker disables Jenkins security
• Assuming Docker only works on Windows
• Believing manual dependency setup is needed

2. Which Docker command correctly runs Jenkins with port 8080 mapped to the host?

easy

A. docker run -p 8080 jenkins/jenkins

B. docker run -p 80:8080 jenkins/jenkins

C. docker run -p 8080:8080 jenkins/jenkins

D. docker run --port 8080:8080 jenkins/jenkins

Solution

1. Step 1: Recall Docker port mapping syntax

   The correct syntax is '-p hostPort:containerPort'.

2. Step 2: Match Jenkins default port

   Jenkins listens on port 8080 inside the container, so map host 8080 to container 8080.

3. Final Answer:

   docker run -p 8080:8080 jenkins/jenkins -> Option C

4. Quick Check:

   Port mapping uses -p host:container = A [OK]

Hint: Use -p hostPort:containerPort for port mapping [OK]

Common Mistakes:

• Using wrong port order in mapping
• Omitting container port
• Using --port instead of -p

3. What will be the effect of running this command?

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

medium

A. Starts Jenkins but data will be lost after container stops

B. Starts Jenkins in detached mode with data persisted in volume 'jenkins_home'

C. Fails because volume name is invalid

D. Runs Jenkins without port mapping

Solution

1. Step 1: Analyze the command flags

   -d runs container detached; -p maps port 8080; -v mounts volume 'jenkins_home'.

2. Step 2: Understand volume usage

   Mounting volume '/var/jenkins_home' preserves Jenkins data outside container lifecycle.

3. Final Answer:

   Starts Jenkins in detached mode with data persisted in volume 'jenkins_home' -> Option B

4. Quick Check:

   Volume mount + detached run = B [OK]

Hint: Volume mounts keep Jenkins data safe across restarts [OK]

Common Mistakes:

• Assuming data is lost without volume
• Confusing detached mode with foreground
• Thinking volume name must be a path

4. You run Jenkins in Docker but get permission errors accessing files. What is a common fix?

medium

A. Run the Jenkins container as root user

B. Remove the volume mount

C. Change Jenkins port to 80

D. Restart Docker daemon

Solution

1. Step 1: Identify cause of permission errors

   Permission errors often occur because Jenkins user inside container lacks rights on mounted files.

2. Step 2: Apply root user workaround

   Running container as root bypasses permission issues by granting full access.

3. Final Answer:

   Run the Jenkins container as root user -> Option A

4. Quick Check:

   Permission fix = run as root [OK]

Hint: Run Jenkins container as root to fix permissions [OK]

Common Mistakes:

• Removing volume loses data
• Changing port doesn't fix permissions
• Restarting Docker unrelated to permissions

5. You want to install Jenkins with Docker ensuring data persists and Jenkins runs on port 9090 on your host. Which command is correct?

hard

A. docker run -d -p 9090:8080 -v jenkins_data:/var/jenkins_home jenkins/jenkins

B. docker run -d -p 8080:9090 -v jenkins_data:/var/jenkins_home jenkins/jenkins

C. docker run -d -p 9090:9090 -v /jenkins:/var/jenkins_home jenkins/jenkins

D. docker run -d -p 8080:8080 -v jenkins_data:/var/jenkins_home jenkins/jenkins

Solution

1. Step 1: Map host port 9090 to Jenkins default port 8080

   Jenkins listens on 8080 inside container, so host port 9090 maps to container 8080.

2. Step 2: Use a volume to persist Jenkins data

   Mount volume 'jenkins_data' to '/var/jenkins_home' to keep data safe across restarts.

3. Final Answer:

   docker run -d -p 9090:8080 -v jenkins_data:/var/jenkins_home jenkins/jenkins -> Option A

4. Quick Check:

   Correct port mapping + volume = C [OK]

Hint: Map host port to 8080 and mount volume for data [OK]

Common Mistakes:

• Swapping port numbers in mapping
• Using wrong volume path
• Not mapping ports correctly