From ed03af2528987a92c09922f5cd701d2ce4a30ad6 Mon Sep 17 00:00:00 2001 From: Cody Hiar Date: Sun, 21 Mar 2021 13:35:51 -0600 Subject: Update README --- README.md | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index cbdea4e..95287a0 100644 --- a/README.md +++ b/README.md @@ -1,17 +1,18 @@ # Docker Jenkins -This is a jenkins repo for building some CI pipelines. - +Run Jenkins in a docker container and give it socket access to build/run other +docker containers. This was an experiement for a presentation I did on docker. ## Lessons Learned -- `/var/jenkins_home` probably needs 777 permissions `docker.sock` probably -- needs 777 permissions since user/groups get confused SSH creds can be -- generated by jenkins user. Git commands require those creds - added into `credentials` and if you have scripts that use ssh then you will - want to add those ssh creds to `publish over ssh` so that pipelines can ssh - into other machines + +- `/var/jenkins_home` probably needs 777 permissions +- `docker.sock` probably needs 777 permissions since user/groups get confused +- SSH creds can be generated by jenkins user. +- Git commands require those creds added into `credentials` and if you have + scripts that use ssh then you will want to add those ssh creds to `publish + over ssh` so that pipelines can ssh into other machines - Keep the filepath of `jenkins_home` the same on host and in container so if - you need volume mounts inside the container, they will be translated - correctly onto the host machine -- Running docker with `userns` will make things more complicated with - user/group translations + you need volume mounts inside the container, they will be translated correctly + onto the host machine +- Running docker with `userns` will make things more complicated with user/group + translations -- cgit v1.2.3