A Jenkins instance which can run docker commands.
Build the Docker image using the Dockerfile in this repo (you may need sudo).
$ docker build -t myjenkins .
Run a container:
$ docker run -d -u root -v /var/run/docker.sock:/var/run/docker.sock -v $(which docker):/usr/bin/docker -v <DIR_OUTSIDE_CONTAINER>:/var/jenkins_home -p 8080:8080 myjenkins
Note that the volume bindings for 'docker.sock' allow docker commands run inside the Jenkins container to spawn containers in the Jenkin container's host.
Once the Jenkins container is running, you can access the Jenkins UI: < IP address or web domain address >:8080 If you are using GCP, you need to add a 'Firewall rules' for port 8080.
Common things you need to do are:
- Add Github credentials (username and password). Go to 'Credentials' and add 'Username with password'.
- Install Plugins with 'Plugin Manager': 'Docker plugin', 'Docker Compose Build Step plugin'
- Install docker-compose in Jenkins container (see below).
The image automatically does this already, but manual steps are never-the-less given here. You need to get a bash shell up in the Jenkins container. First, find the container name/id of the Jenkins container:
$ docker ps
Then:
$ docker exec -it <container_name/id> bash
Once inside, follow the instructions:
https://docs.docker.com/compose/install/
This is needed in order for Jenkins to clone code from your Github. Git a bash shell up in the Jenkins container (docker exec -it <jenkins_container_name> bash). Then, do:
$ ssh-keygen
Once the key is made, add the public key to your Github account 'Settings' -> 'SSH and GPG keys'. Note, the first time you pull a repository it asks:
Are you sure you want to continue connecting (yes/no)? yes It requires an interactive response of 'yes'. It is recommended you go to /home/ (still inside docker container) and do a 'git clone' for the first time and enter 'yes' manually. After this, you can Jenkins project builders can 'got clone' without issue.