About Fedora containers

[Alejandro Saez Morollon]

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] About Fedora containers

[Lumír Balhar]

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(a)redhat.com 
- 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(a)lists.fedorahosted.org
>  To unsubscribe send an email to container-sig-leave(a)lists.fedorahosted.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.fedorahosted.org/archives/list/[e-mail]...
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Container-sig] About Fedora containers

[Matthew Miller]

On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
>  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. 
I wonder if we should just... make this official? It seems like a pretty
easy way to create and maintain an official library of layered images which
are made of Fedora packages — like, some language-base ones like golang or
python, plus nginx, apache, postgresql, etc.


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Container-sig] About Fedora containers

[Josh Boyer]

On Tue, Jun 21, 2022 at 3:42 PM Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>  On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
>  > 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.
>
>  I wonder if we should just... make this official? It seems like a pretty
>  easy way to create and maintain an official library of layered images which
>  are made of Fedora packages — like, some language-base ones like golang or
>  python, plus nginx, apache, postgresql, etc. 
Yes.

josh

[Container-sig] About Fedora containers

[Kevin Fenzi]

On Tue, Jun 21, 2022 at 03:41:47PM -0400, Matthew Miller wrote:
>  On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
>  > 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.
>  
>  I wonder if we should just... make this official? It seems like a pretty
>  easy way to create and maintain an official library of layered images which
>  are made of Fedora packages — like, some language-base ones like golang or
>  python, plus nginx, apache, postgresql, etc. 
Yes, thats the plan... but as always it's not just "flip a switch and
drive on". We need to make sure all the features we use are available at
quay.io, that tooling has changes so we can push there, etc. 

https://pagure.io/fedora-infrastructure/issue/10386

Note that this is just moving things in our registry over there and
pointing everyone to it so we can get out of the registry business, we
haven't looked at building the containers there or the like. We are
hoping osbuilder will help us here (or osbs 2.0). 

kevin

[Container-sig] About Fedora containers

[Blaise Pabon]

I wonder if, rather than Github, we should consider a more "open source"
toolchain, eg opendev.org, gitlab, etc. to be more consistent with
Fedora's  "free" vision?

On Wed, Jun 22, 2022 at 11:57 AM Kevin Fenzi <kevin(a)scrye.com&gt; wrote:

>  On Tue, Jun 21, 2022 at 03:41:47PM -0400, Matthew Miller wrote:
>  > On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
>  > > 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.
>  >
>  > I wonder if we should just... make this official? It seems like a pretty
>  > easy way to create and maintain an official library of layered images
>  which
>  > are made of Fedora packages — like, some language-base ones like golang
>  or
>  > python, plus nginx, apache, postgresql, etc.
>
>  Yes, thats the plan... but as always it's not just "flip a switch and
>  drive on". We need to make sure all the features we use are available at
>  quay.io, that tooling has changes so we can push there, etc.
>
>  https://pagure.io/fedora-infrastructure/issue/10386
>
>  Note that this is just moving things in our registry over there and
>  pointing everyone to it so we can get out of the registry business, we
>  haven't looked at building the containers there or the like. We are
>  hoping osbuilder will help us here (or osbs 2.0).
>
>  kevin
>  _______________________________________________
>  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/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 
LinkedIn <https://www.linkedin.com/in/blaisepabon/>  |  Quora
<https://www.quora.com/profile/Blaise-Pabon>  |  Github
<https://github.com/blaisep>
“If you want to go fast, go alone. If you want to go far, go
together.” --African
proverb

[Container-sig] About Fedora containers

[Kevin Fenzi]

On Thu, Jun 23, 2022 at 09:11:13AM -0400, Blaise Pabon wrote:
>  I wonder if, rather than Github, we should consider a more "open
> source"
>  toolchain, eg opendev.org, gitlab, etc. to be more consistent with
>  Fedora's  "free" vision? 
Not sure what github has to do with things here? 

quay is open source... althought quay.io is a Red Hat run instance of
that. 

kevin
--
>  
>  On Wed, Jun 22, 2022 at 11:57 AM Kevin Fenzi <kevin(a)scrye.com&gt; wrote:
>  
>  > On Tue, Jun 21, 2022 at 03:41:47PM -0400, Matthew Miller wrote:
>  > > On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
>  > > > 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.
>  > >
>  > > I wonder if we should just... make this official? It seems like a pretty
>  > > easy way to create and maintain an official library of layered images
>  > which
>  > > are made of Fedora packages — like, some language-base ones like golang
>  > or
>  > > python, plus nginx, apache, postgresql, etc.
>  >
>  > Yes, thats the plan... but as always it's not just "flip a switch and
>  > drive on". We need to make sure all the features we use are available at
>  > quay.io, that tooling has changes so we can push there, etc.
>  >
>  > https://pagure.io/fedora-infrastructure/issue/10386
>  >
>  > Note that this is just moving things in our registry over there and
>  > pointing everyone to it so we can get out of the registry business, we
>  > haven't looked at building the containers there or the like. We are
>  > hoping osbuilder will help us here (or osbs 2.0).
>  >
>  > kevin
>  > _______________________________________________
>  > 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/[e-mail]
>  > Do not reply to spam on the list, report it:
>  > https://pagure.io/fedora-infrastructure
>  >
>  
>  
>  -- 
>  LinkedIn <https://www.linkedin.com/in/blaisepabon/>  |  Quora
>  <https://www.quora.com/profile/Blaise-Pabon>  |  Github
>  <https://github.com/blaisep>
>  “If you want to go fast, go alone. If you want to go far, go
>  together.” --African
>  proverb 
>  _______________________________________________
>  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/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Container-sig] About Fedora containers

[Maxwell G]

On Thursday, June 23, 2022 1:50:09 PM CDT Kevin Fenzi wrote:
>  Not sure what github has to do with things here? 
Lumír said:

>  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. 
However, it doesn't sound to me like Github Actions is related to this 
proposal; that's just how the Python SIG happens to publish their container 
images to quay.io.

-- 
Thanks,

Maxwell G (@gotmax23)
Pronouns: He/Him/His

[Container-sig] About Fedora containers

[Blaise Pabon]

Sorry, I read this as becoming dependent on GitHub actions for CI and for
CD.

On Thu, Jun 23, 2022, 4:24 PM Maxwell G via devel <
devel(a)lists.fedoraproject.org&gt; wrote:

>  On Thursday, June 23, 2022 1:50:09 PM CDT Kevin Fenzi wrote:
>  > Not sure what github has to do with things here?
>
>  Lumír said:
>
>  > 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.
>
>  However, it doesn't sound to me like Github Actions is related to this
>  proposal; that's just how the Python SIG happens to publish their
>  container
>  images to quay.io.
>
>  --
>  Thanks,
>
>  Maxwell G (@gotmax23)
>  Pronouns: He/Him/His_______________________________________________
>  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/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Container-sig] About Fedora containers

[Matthew Miller]

On Wed, Jun 22, 2022 at 08:57:24AM -0700, Kevin Fenzi wrote:
>  Note that this is just moving things in our registry over there and
>  pointing everyone to it so we can get out of the registry business, we
>  haven't looked at building the containers there or the like. We are
>  hoping osbuilder will help us here (or osbs 2.0).  

Quay has a really easy integration where it can build containers
automatically from a dockerfile in a GitLabor Github repo (and that could
probably be extended to other things). I think that we should use that for
everything but base images (of course).

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Container-sig] About Fedora containers

[Daniel P. Berrangé]

On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
>  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. 
So are you saying that registry.fedoraproject.org is obsolete and
should not be used anymore ?

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

[Container-sig] About Fedora containers

[Daniel Walsh]

On 6/22/22 10:04, Daniel P. Berrangé wrote:
>  On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
> > 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.
>  So are you saying that registry.fedoraproject.org is obsolete and
>  should not be used anymore ?
>
>  With regards,
>  Daniel 
Can it be setup as a redirector to the quay.io site?

[Petr Hracek]

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/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure