#23 Allow me to build multiple versions of container image per fedora release
Opened 5 years ago by praiskup. Modified 5 years ago

This is maybe only a question how to achieve the $Summary. We have now modularized PostgreSQL server in Fedora 28+, which gives us ATM three options how to build PostgreSQL container image, from version 9.6/10 or 11. We'd like to build all the three options (and add more in future).

At this point, for F29 we only have f29/postgresql image. So I'd like to have something like postgresql-9.6-fedora29, postgresql-10-fedora29, etc., or e.g.
f29/postgresql:9.6, f29/postgresql:10 and f29/postgresql:11. Is this possible?

This might be related to #2, dunno. Feel free to ping me on irc (#praiskup).


@praiskup So I think indeed this is related to #2 and also #7 and I think technically OSBS should support such a use case.

I think we need to give it a try and see if that works well update our guidelines and create some documentation.

I ll be happy to help, I ll look at creating a PR for the postgresql container and we can use this PR to discuss implementation etc ...

Feel free to join #fedora-containers on freenode

I have opened https://src.fedoraproject.org/container/postgresql/pull-request/1#request_diff

This should set the base for you to use modularity and start managing version in stream branches instead of the current release branches.

So, how can I request stream branches? Will OSBS build just work if I'll do fedpkg container-build in newly created stream branches? How am I supposed to name them?

After f2f discussion with @cverna and other guys from RH container team, the easiest step forward should be to use container.yml file, and start producing tags like 10_f28, etc. so we would have postgresql:{96,10,11}_f{28,29}. The thing is that it requires either 2x3=6 "stream" branches (can those be created for me?), or we have to have the tooling a little bit smarter -- e.g. we could have one branch for one PostgreSQL version (v10 e.g.) and then use docker ARGS to differentiate the FROM statement, and then we could hit e.g. one fedpkg container-build in stream branch 10.

I have opened https://pagure.io/ContainerSIG/container-sig/issue/24 with what is needed to get stream branches for containers.

Login to comment on this ticket.

Metadata