jenkinsci/docker

★ 7,491PowerShellAudience · ops devopsComplexity · 3/5Setup · moderate

Mindmap

mindmap
  root((Jenkins Docker))
    Quick start
      Single docker run
      Web UI port 8080
      Agent port 50000
    Persistence
      Named volume
      jenkins_home folder
    Configuration
      Init scripts
      Plugin install
      HTTPS setup
    Deployment
      Reverse proxy
      Docker Compose
      DNS fix

mindmap root((Jenkins Docker)) Quick start Single docker run Web UI port 8080 Agent port 50000 Persistence Named volume jenkins_home folder Configuration Init scripts Plugin install HTTPS setup Deployment Reverse proxy Docker Compose DNS fix

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Start a Jenkins CI server in minutes using Docker and persist all pipelines, plugins, and job history with a named volume.

USE CASE 2

Automatically install plugins and custom configuration at container startup using init scripts for a reproducible Jenkins environment.

USE CASE 3

Run Jenkins behind a reverse proxy so it is accessible at a path like mysite.com/jenkins rather than directly on a port.

USE CASE 4

Set up Jenkins alongside other services using Docker Compose for a local or staging development environment.

Tech stack

DockerJavaJenkinsPowerShell

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Docker, must mount jenkins_home as a named volume or all data is lost when the container restarts.

No license information specified in the README.

In plain English

This repository contains the official Docker image for Jenkins, a widely used automation server that teams set up to run tests, build software, and deploy code automatically. If you have heard of continuous integration or CI/CD pipelines, Jenkins is one of the oldest and most established tools in that space. The image lets you start a fully working Jenkins server with a single command. You expose two ports: one for the web interface where you log in and manage your pipelines, and another that worker machines called agents connect to when they pick up build jobs. Your Jenkins settings, installed plugins, and job history all live in a folder called jenkins_home, and the README strongly recommends mounting that folder as a named Docker volume so your data survives container restarts and upgrades. The README covers a range of setup scenarios. You can pass extra memory or system settings to the Java runtime that Jenkins runs on. You can configure how Jenkins writes its logs. You can place Jenkins behind a web proxy if your team accesses it through a path like mysite.com/jenkins rather than directly. There is also a section on DNS problems that sometimes appear on first startup, with a fix involving specifying a public DNS server when you start the container. For teams that want to add plugins or custom configuration automatically, the image supports an init scripts folder where you can drop files that Jenkins reads on startup. The README also covers how to install plugins in advance, how to set up HTTPS by baking a certificate into a custom image, and how to run Jenkins in a Docker Compose setup alongside other services. This image is maintained by the Jenkins project itself. It is intended for teams comfortable with Docker who want a fast path to a working Jenkins environment without installing Jenkins manually on a server.

Copy-paste prompts

Prompt 1

Write a docker-compose.yml that runs the official Jenkins Docker image with a named volume for jenkins_home, exposes the web UI on port 8080, and the agent port on 50000.

Prompt 2

How do I build a custom Docker image based on jenkinsci/docker that pre-installs a specific set of Jenkins plugins so they are ready when the container starts?

Prompt 3

My Jenkins Docker container has DNS resolution errors on first startup. What flag do I add to the docker run command to point it at a public DNS server?

Prompt 4

Show me how to configure the official Jenkins Docker image to run behind an nginx reverse proxy at the path /jenkins with correct URL prefix settings.

Open on GitHub → Explain another repo

← jenkinsci on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.