Hi all!
TL;DR: Is there any documentation about how to properly take care of
our containers? :)
---
The Go container has been outdated for a while, and I would love to
update it[0], but I'm not familiar with the container process in
Fedora.
I checked Python3's container[1] looking for information, and I saw
that the rawhide branch is not used in the same way we use it with the
RPMs.
Also, I saw that the s2i-base image is only available until F35. No
F36 or Rawhide.
And, it looks like they are only available for x86_64 platforms.
So I guess the main big question is: is there any documentation or
proposals I should be aware of? Is the Go container relevant?
cc'ed Container SIG's mailing list; I didn't see movement in the
mailing list, just in case.
[0] https://src.fedoraproject.org/container/golang
[1] https://src.fedoraproject.org/container/python3
Thank you very much!
Hi all,
A few of us met Saturday to discuss the future of the SIG below are the
minutes of the discussions we had.
* Future of the SIG (What we want to do)
* Defining short term and long term goals and action items for the SIG
We looked at our mission statement [0] and felt that it still reflects
correctly our goals, we then discussed some sub objectives :
- maintain the fedora base image
- improve the maintainer experience for layered image
- help the OKD community to contribute images so that they can use them in
the OKD catalog
About the fedora base image, we discussed following the Fedora Change
process and announcing the changes to the base image in a self contained
change. There might also be a possibility to use Bodhi for the base image.
Regarding the maintainer experience we discussed a few things :
- Automatic rebuild of the layered image when the base image is updated (
This sounds like a priority we want to focus on [1])
- We need more documentation and in particular around maintaining a
layered image [2]
We quickly discussed the Packaging guidelines and review process and
decided that proposing changes via PR on the docs repo is a good way to
discuss changes.
Finally we agreed to use async communication as much as possible and
organize a Hackfest/Fedora Activity Day when needed.
Thanks all
Clément
[0] - https://fedoraproject.org/wiki/Container_SIG#Fedora_Container_SIG
[1] - https://github.com/containerbuildsystem/atomic-reactor/issues/963
[2] - https://github.com/containers/docs