ppollai/jenkins repository overview

⁠Customized Jenkins Docker Image with 137 Pre-installed Usefull Plugins.

The Jenkins Continuous Integration and Delivery server.

This is a fully functional Jenkins server, based on the LTS releases .

It has pre-installed 137 plugins.

Also default admin user is created on this, so NO neeed to wait for startup initialzation.

Default username is:

admin

And password is:

password

⁠Usage

docker run -d -p 8080:8080 -p 50000:50000 --restart=on-failure ppollai/jenkins:lts

This will store the workspace in /var/jenkins_home. All Jenkins data lives in there - including plugins and configuration. You will probably want to make that an explicit volume so you can manage it and attach to another container for upgrades :

docker run -d -p 8080:8080 -p 50000:50000 --restart=on-failure -v jenkins_home:/var/jenkins_home ppollai/jenkins:lts

This will automatically create a 'jenkins_home' docker volume⁠ on the host machine. Docker volumes retain their content even when the container is stopped, started, or deleted.

NOTE: Avoid using a bind mount⁠ from a folder on the host machine into /var/jenkins_home, as this might result in file permission issues (the user used inside the container might not have rights to the folder on the host machine). If you really need to bind mount jenkins_home, ensure that the directory on the host is accessible by the jenkins user inside the container (jenkins user - uid 1000) or use -u some_other_user parameter with docker run.

docker run -d -v jenkins_home:/var/jenkins_home -p 8080:8080 -p 50000:50000 --restart=on-failure ppollai/jenkins:lts

This will run Jenkins in detached mode with port forwarding and volume added. You can access logs with command 'docker logs CONTAINER_ID' in order to check first login token. ID of container will be returned from output of command above.

The Jenkins container is based on the jenkins/jenkins:lts image and exposes the Jenkins web interface on port 8080. The jenkins_home volume is a named volume⁠ that is created and managed by Docker.

It is mounted at /var/jenkins_home in the Jenkins container, and it will persist the Jenkins configuration and data.

The ssh-agent container is based on the jenkins/ssh-agent image and runs an SSH server to execute Jenkins SSH Build Agent⁠.

To start the Jenkins instance and the other services defined in the docker-compose.yml file, run the docker compose up -d.

This will pull the necessary images from Docker Hub if they are not already present on your system, and start the services in the background.

You can then access the Jenkins web interface on http://localhost:8080 on your host system to configure and manage your Jenkins instance (where localhost points to the published port by your Docker Engine).