Installing with Docker in Jenkins - Practice Exercises

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Docker Container Startup Output

You run the command to start Jenkins in Docker:

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

What output will you see first in the Docker logs indicating Jenkins is ready to use?

Jenkins

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

A Error: Port 8080 is already in use

B Jenkins initialAdminPassword: /var/jenkins_home/secrets/initialAdminPassword

C Jenkins is fully up and running

D Jenkins initial setup wizard is complete

💡 Hint

Look for the file path where Jenkins stores the initial admin password.

When Jenkins starts in Docker for the first time, it outputs the location of the initial admin password file. This is shown as 'Jenkins initialAdminPassword: /var/jenkins_home/secrets/initialAdminPassword'.

❓ Configuration

intermediate

Correct Docker Run Command for Jenkins with Volume

Which Docker command correctly runs Jenkins with persistent data stored on the host at /home/user/jenkins_home?

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

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

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

D docker run -p 8080:8080 -v /home/user/jenkins_home jenkins/jenkins:lts

💡 Hint

Remember the format for Docker volume mapping is host_path:container_path.

Option C correctly maps the host directory to the Jenkins home directory inside the container, ensuring data persists outside the container.

❓ Troubleshoot

advanced

Jenkins Docker Container Fails to Start

You try to start Jenkins with:

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

The container exits immediately. What is the most likely cause?

A Port 8080 is already in use on the host

B Docker daemon is not running

C Jenkins image is missing from local Docker cache

D The container requires a volume mount for /var/jenkins_home

💡 Hint

Check if another service is using the port Jenkins needs.

If port 8080 is busy, Docker cannot bind it and the container exits immediately with an error.

🔀 Workflow

advanced

Steps to Upgrade Jenkins Docker Container

What is the correct sequence to upgrade Jenkins running in Docker to a newer version without losing data?

A 1,2,3,4

B 2,3,1,4

C 1,3,2,4

D 2,1,3,4

💡 Hint

You must stop the old container before starting a new one with the updated image.

First stop the old container to free resources, then pull the new image, start a new container with the existing data volume, and finally verify everything works.

✅ Best Practice

expert

Secure Jenkins Docker Installation

Which practice best improves security when running Jenkins in Docker?

A Disable Jenkins authentication to simplify access

B Expose Jenkins ports to all network interfaces

C Run Jenkins container as root user for full access

D Use Docker secrets or environment variables for sensitive data

💡 Hint

Think about how to protect passwords and tokens in Docker.

Using Docker secrets or environment variables keeps sensitive data out of code and images, reducing risk of leaks.

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