What keeps container maintainers awake
summary
Container maintainers treat Dockerfiles plus helper scripts as the true upstream source and consolidate versions into one repo per stack to avoid duplication, juggling 38 images on RHEL7 and ~15 per Fedora release. Duplication is solved either with symlinks or a small Python generator using make generate with Jinja2 to produce per-platform files. Rebuild cadence targets every three weeks on RHEL (historically two on Fedora) to fix CVEs, driven by automation like Freshmaker and OSBS chain rebuilds, with GitHub sync handled by Bitkha bots.
AI-written summary · about
chapters (9)
- 0:00Container maintenance challenges
- 2:40RPM vs container maintenance
- 6:31Missing upstream sources
- 10:46Automating image generation
- 11:06Syncing upstream and downstream
- 13:15Rebuilding images for CVEs
- 15:28Automation tools
- 18:43Manual batch tools
- 21:13Extending container images
related talks
33mDocker Container Lifecycles – Problem or Opportunity?
20mEmerging Automated License Compliance for Containers
32mBalancing Developer Fre...
14mUsing packit and testing farm for CI/CD and automation in an upstream project
40m"Willy Wonka and the Secure Container Factory"
44mDocker for DevSecOps
40mA Maintainer's Odyssey: Time, Technology, and Transformation
35mForeman, Katello and bootable containers