Re: About Fedora containers
Hi Alejandro,
we have developed an easy GitHub Action [1].
The example how to use it is already mentioned in README.md [2].
All our images are automatically by merging PR pushed into Quay.io.
See an examples GitHub Action here [3].
As you can see the nginx-container image is automatically pushed to Quay.io
when the PR is merged or regularly each Wednesday.
[1] https://github.com/sclorg/build-and-push-action/
[2] https://github.com/sclorg/build-and-push-action/blob/main/README.md
[3]
https://github.com/sclorg/nginx-container/blob/master/.github/workflows/b...
On 17.06.2022 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!
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure