Slides from my talk at CentOS Dojo before FOSDEM in Brussels. These slides give an overview of the features of CentOS Container Pipeline.

1. Introducing
CentOS Container Pipeline
registry.centos.org

3. Imagine
● You maintain 10 images
● All images are based on
same image
● Base image gets updated

4. No big deal; it’s just 10 images

5. What if there were 100?

6. CentOS Container Pipeline...
● Does automatic rebuilds in such case
● Also rebuilds upon “git push”
● Doesn’t just do “docker build”
○ Lints the Dockerfile
○ Pre-builds the binaries/artifacts
○ Builds the image
○ Scans it

7. What does it scan for?
● RPM updates
● pip, npm, gem updates
● RPM verification
● Container capabilities
● Weekly scanning

8. Workflow

10. Example yaml file

11. Why yet another pipeline?
● No solution to lint, build, scan images on regular basis
● No triggers other than code push to git repo
● Limited scanning capabilities; available for a cost
● No regular scan reports on all the images
● No dependency between images (parent-child relationship)
● No open source solution to do all of these!

12. Work in
progress
● API and UI integration
for logs
● Moving away from docker
build to buildah
● Rebuilds on RPM update

13. What does the
community think?

14. Links
● registry.centos.org
● https://github.com/CentOS/container-pipeline-service/
● https://github.com/CentOS/container-index/

15. Thank you!