Hello.
Because we had a lot of troubles with Fedora infra for container images
(I can provide more details, if you want), we have decided to move our
containers to https://quay.io/organization/fedora.
With quay.io, we are able to produce new container images directly from
Github CI and rebuild them regularly without complicated update process
and without any need to maintain sources for in the dedicated dist git.
I see that the upstream repository for golang container is also kinda
outdated so I'd start there, update it and then ping phracek@xxxxxxxxxx
- Petr will help you set up CI for the container image and publish it to
Quay.io.
Have a nice day.
Lumír
On 6/17/22 15:59, Alejandro Saez Morollon wrote:
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!
_______________________________________________
Container-sig mailing list -- container-sig@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to container-sig-leave@xxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/container-sig@xxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
