In an OS distribution like Fedora, sooner or later there will be need for maintainers who care about container images, instead of RPM packages. Similarly to RPM spec files, those people will care about specs for containers, currently called Dockerfiles.
What is the challenge here? Linux containers are by design static, so it might need a bit of invention to make the container image flexible enough for different users' use cases. Another issue comes together with rebuilds, that are needed every-time some security fix affects the container, so the testing needs to be fully automated.
We faced those and other challenges during development of RHSCL container images (http://github.com/sclorg/), and this break-out talk will introduce some innovative concepts and automation tips that we've been using.
Who is the audience for this?
The best match would be a "container maintainer", aka a container-image-focused variant for a package maintainer. But I think general users of container images would benefit from that as well.
Metadata Update from @bex: - Issue tagged with: Talk In Consideration
For Flock, can you update the title and abstract (and of course, eventually, talk content) to focus more on the "container maintainer" angle? I'm +1 to this in that case. If we want to talk to general users, we should send this talk to ContainerCon or something. (Which I'd be interested in doing, by the way.)
I've updated the description, not sure whether it is any better now :) Anyway, feel free to suggest the direction, and I might reconsider, whether I can contribute in that regard.
I regret that we are unable to accept this talk this year. There will be lightning talk sessions and I encourage you to consider this option.
Metadata Update from @bex: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.