I maintain python3 image together with s2i-base and core. I'm trying to make my life easier and implement some kind of automation to be able to build all the images at once.
I see that there is this option for fedpkg container-build - --koji-parent-build, but I don't know how to use it. I've built s2i-core (https://koji.fedoraproject.org/koji/taskinfo?taskID=72289741) and now I'd like to build s2i-base on top of it. Is it possible to use the s2i-core from the candidate registry as a parent image for the next build of s2i-base?
fedpkg container-build
--koji-parent-build
I'd be perfect to make It possible so I'd be able to build all of them in one row and then create updates from the builds. Now I have to do that one by one and always wait for the update to appear in the registry before I can rebuild the next image in the queue.
Cc @hhorak @phracek @pkubat
I honestly don't know how this is supposed to work :) . Maybe @athoscr would have an idea ?
I've dived deeper in the waters of fedpkg, koji, and atomic-reactor and found out that the proper format is the numeric build id like this: fedpkg container-build --scratch --koji-parent-build 1720423
fedpkg container-build --scratch --koji-parent-build 1720423
The command above builds python3 container for Fedora 34 with an older s2i-base than the latest one we have - this might be also useful in some situations. But the problem I have is still not solved because I cannot use a build id of a container that is not yet pushed to the main registry.
Login to comment on this ticket.