![Jenkins]()
Jenkins
Container
Open-source continuous integration tool
Image details
Configuration
TypeContainerlinuxjenkins/jenkins:lts8080/tcp50000/tcp/var/jenkins_homeJENKINS_OPTS=''Template by mikestraney
Standalone Install
Select an install method, to see config/commands for deploying Jenkins
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Jenkins, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation.
Jenkins Continuous Integration and Delivery server.
This is a fully functional Jenkins server, based on the weekly and LTS releases .
- Short JDK (Weekly builds) and LTS tags correspond to Debian images,
latest(not recommended) is a Debian image with the current default JDK - Lighter Alpine, Debian Slim, RedHat family, Windows and other JDKs based image also available
- (Recommended) Specific versions (to be pinned) are also available.
Read documentation in our README at github.com/jenkinsci/docker for more details and usage.
Serve Jenkins on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying jenkins.example.com to http://jenkins:8080
Add this to your Caddyfile
jenkins.example.com {
reverse_proxy http://jenkins:8080
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Published on a random port
This template exposes 8080/tcp without setting a host port,
so Docker picks a random free one on every deploy.
- Find it in the Ports column of Portainer's container list, or with
docker port <container>
Image won't pull
Test the pull directly on the host: docker pull jenkins/jenkins:lts
- "manifest unknown" means the tag no longer exists.
- "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64, ppc64le, s390x, riscv64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Required settings are blank
JENKINS_OPTS has no default value, and the app may crash or misbehave if left empty.
- Fill it in on the deploy screen before hitting deploy.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within the app's repo
- Template not working: Open an issue on mikestraney/portainer-templates
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Jenkins runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Jenkins needs bundled into one download. This template pulls jenkins/jenkins:lts, which Docker fetches once (about 231 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Jenkins's comes from Docker Hub, published by jenkins.
Version tags
The bit after the colon in the image name is the version tag. This one pins lts, so every redeploy gives you that exact build until you bump it yourself.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, ppc64le, s390x, riscv64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:
8080, published on a random host port50000, published on a random host port
Volumes
A volume is where Jenkins keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/var/jenkins_homeas a volume Docker manages for you
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Jenkins takes 1 of them, and one needs a value before it'll start properly:
JENKINS_OPTS, needs a value. Jenkins options
Networking
Nothing custom is set, so Jenkins sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Jenkins up. Add the template list to Portainer once, then deploying Jenkins is a click rather than a wall of config.