The upstream OSBS development group has had to push out the deadlines for the automated rebuild work and Factory 2.0 isn't ready yet (it wasn't planned to be, but it is noted for posterity) which means that Fedora needs to make a decision on how we will handle container image updates. We're targeting releases every two weeks but in order to get rpm content updates automatically included and parent image update inheritance taken into consideration we will need to write some automation tooling to accomplish that until both OSBS layered rebuilds are done and Factory 2.0 rpm-content triggered rebuild work is completed.
The question to the group is: do we want to force a rebuild of all content before each container image release (likely the day before) in the mean time?
The reason we can't realistically detect when/if content changes that would require a rebuild is because the Factory 2.0 work that is still ongoing is what will create the content database(PDC/resultsdb) to track the relationship between a set of rpms and a container image.
We should do what's needed to ensure that our images pick up the most recent rpms -- when you say rebuild all content, do you mean rebuild the rpms themselves, or rebuild all the images?
Sorry for lack of clarification, I meant "Rebuild all images" which would pull in the latest stable rpms without requiring maintainer intervention.
We should do what's needed to ensure that our images pick up the most recent rpms -- when you say rebuild all content, do you mean rebuild the rpms themselves, or rebuild all the images? Sorry for lack of clarification, I meant "Rebuild all images" which would pull in the latest stable rpms without requiring maintainer intervention.
I am +1 to this idea.
Agreed that we will rebuild container images to include updates before each release.
EDIT: It was agreed upon during the atomic-wg meeting.
+1 to rebuilding containers regularly - we may have to revisit this as the number of containers we support increases.
Metadata Update from @maxamillion: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.