hhorak reported a new issue against the project: `atomic-wg` that you are following:
Let me describe my frustration from building layered containers in Fedora.
We've been maintaining CentOS and RHEL based images for various interesting stuff like
databases (PostgreSQL, MariaDB) or dynamic languages (Python, NodeJS) at
and we'd love to see the same set of containers in Fedora as
The challenge I see is that we have 2 or 3 layers on top of the base image, e.g.: Fedora
28 -> s2i-core -> s2i-base -> python, which is probably somewhat special,
comparing to simple container images that just depend on the base image. The problem is
that when we want to build either s2i-base or python, we only can take image from the
release registry (registry.fedoraproject.org
, mentioned in the guidelines and enforced in
the tooling), so if the release would work as expected every two weeks, we can build
s2i-core, in 2 weeks we can build s2i-base, and in another two weeks we can have up2date
python container that uses some features from s2i-core that we built 4 weeks back.. That
is not what we want to see.
And then, there is the release itself, that is still somewhat indeterministic, and we
don't see when the built image will be available.
Anyway, when thinking about how to fix this process issue, it looks like everything would
be better if layered images from the *candidate* registry would be used when building a
new container. It might be done simply by rewriting `FROM`
(`s/registry.fedoraproject.org/candidate-registry.fedoraproject.org/`) as such rewrites
are done anyway in OSBS... If someone would really like to use the image from released
registry, they can use concrete release tag..
What do you think?
To reply, visit the link below or just reply to this email