diff options
| author | Cody Hiar <codyfh@gmail.com> | 2019-04-14 15:30:30 -0600 |
|---|---|---|
| committer | Cody Hiar <codyfh@gmail.com> | 2019-04-14 15:30:30 -0600 |
| commit | e8ae2101007031d30898154a733167e8c3696ee8 (patch) | |
| tree | 2bf894550db6a8a2497898b9387584e1c78a7206 | |
| parent | 5739d2832c14a51743a25cb5974719d4bb927128 (diff) | |
Adding lessons learned
| -rw-r--r-- | README.md | 18 |
1 files changed, 10 insertions, 8 deletions
@@ -4,12 +4,14 @@ This is a jenkins repo for building some CI pipelines. ## 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 + 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 |