Hi, For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx. I've started using these Actions: https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action docs: https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima... These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers. Are there equivalent GitHub Actions for using podman? I still think that podman/buildah are overall better tools for building containers than Docker. -- Craig
Craig, I think this is a question for GitHub, as Red Hat doesn't definitively know what GitHub software does. That said, I did a quick look at this [1] and see that "GitHub provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows" so I doubt it. So, in a perfect world, I'd file an RFE with GitHub for: 1. Add RHEL/Fedora option as a runner 2. Add actions for Podman If you file these, this is something I can definitely push with our partner team who works with GitHub. [1]: https://docs.github.com/en/actions/learn-github-actions/understanding-github... Best Regards Scott M On Thu, May 26, 2022 at 12:43 PM Craig Rodrigues <rodrigc@crodrigues.org> wrote:
Hi,
For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx.
I've started using these Actions:
https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action
docs:
https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima...
These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers.
Are there equivalent GitHub Actions for using podman?
I still think that podman/buildah are overall better tools for building containers than Docker. -- Craig
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
-- <https://www.redhat.com/en/about/press-releases/red-hat-defines-new-epicenter-innovation-red-hat-enterprise-linux-9> Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
Let me clarify. I think #1 is for Microsoft #2 is probably for the Podman project. My 2c. On Thu, May 26, 2022 at 2:31 PM Scott McCarty <smccarty@redhat.com> wrote:
Craig, I think this is a question for GitHub, as Red Hat doesn't definitively know what GitHub software does. That said, I did a quick look at this [1] and see that "GitHub provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows" so I doubt it.
So, in a perfect world, I'd file an RFE with GitHub for: 1. Add RHEL/Fedora option as a runner 2. Add actions for Podman
If you file these, this is something I can definitely push with our partner team who works with GitHub.
[1]: https://docs.github.com/en/actions/learn-github-actions/understanding-github...
Best Regards Scott M
On Thu, May 26, 2022 at 12:43 PM Craig Rodrigues <rodrigc@crodrigues.org> wrote:
Hi,
For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx.
I've started using these Actions:
https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action
docs:
https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima...
These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers.
Are there equivalent GitHub Actions for using podman?
I still think that podman/buildah are overall better tools for building containers than Docker. -- Craig
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
--
Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
-- <https://www.redhat.com/en/about/press-releases/red-hat-defines-new-epicenter-innovation-red-hat-enterprise-linux-9> Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
It looks like a fedora runner was already asked for, and the suggestion was to use a container runner or self hosted runner with fedora because they were concerned about the overhead of maintaining another runner. (I suspect) the container solution works for building software but might have issues building other containers. Here is the discussion: https://github.com/actions/virtual-environments/issues/2307 That said, that issue was 2 years ago and it wouldn't hurt to ask again. :) Something something... squeaky wheel... 🎡 On Thu, May 26, 2022 at 12:34 PM Scott McCarty <smccarty@redhat.com> wrote:
Let me clarify. I think #1 is for Microsoft #2 is probably for the Podman project. My 2c.
On Thu, May 26, 2022 at 2:31 PM Scott McCarty <smccarty@redhat.com> wrote:
Craig, I think this is a question for GitHub, as Red Hat doesn't definitively know what GitHub software does. That said, I did a quick look at this [1] and see that "GitHub provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows" so I doubt it.
So, in a perfect world, I'd file an RFE with GitHub for: 1. Add RHEL/Fedora option as a runner 2. Add actions for Podman
If you file these, this is something I can definitely push with our partner team who works with GitHub.
[1]: https://docs.github.com/en/actions/learn-github-actions/understanding-github...
Best Regards Scott M
On Thu, May 26, 2022 at 12:43 PM Craig Rodrigues <rodrigc@crodrigues.org> wrote:
Hi,
For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx.
I've started using these Actions:
https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action
docs:
https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima...
These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers.
Are there equivalent GitHub Actions for using podman?
I still think that podman/buildah are overall better tools for building containers than Docker. -- Craig
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
--
Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
--
Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Scott, I think you are confusing two things. A. How the GitHub platform works B. What a GitHub Action is While it is useful to know about A., I am more interested in B., and having GitHub Actions implemented for podman. In my initial e-mail, I posted links to various GitHub Actions which are implemented in GitHub Repositories. These Actions can be used to do various things like install docker toolchains, build containers, and push containers to registries, all using GitHub runner infrastructure. The actual implementation of these GitHub Actions is done in various languages. For example, https://github.com/docker/build-push-action is implemented inTypeScript/JavaScript. Actions implemented in the https://github.com/docker organization are implemented by Docker (the company), so it is unlikely that they would be interested in adding podman support to these Actions. If there were a set of equivalent GitHub Actions implemented in the https://github.com/containers organization that worked with podman/buildah, that might be interesting to have. -- Craig On Thu, May 26, 2022 at 2:32 PM Scott McCarty <smccarty@redhat.com> wrote:
Craig, I think this is a question for GitHub, as Red Hat doesn't definitively know what GitHub software does. That said, I did a quick look at this [1] and see that "GitHub provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows" so I doubt it.
So, in a perfect world, I'd file an RFE with GitHub for: 1. Add RHEL/Fedora option as a runner 2. Add actions for Podman
If you file these, this is something I can definitely push with our partner team who works with GitHub.
[1]: https://docs.github.com/en/actions/learn-github-actions/understanding-github...
Best Regards Scott M
On Thu, May 26, 2022 at 12:43 PM Craig Rodrigues <rodrigc@crodrigues.org> wrote:
Hi,
For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx.
I've started using these Actions:
https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action
docs:
https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima...
These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers.
Are there equivalent GitHub Actions for using podman?
I still think that podman/buildah are overall better tools for building containers than Docker. -- Craig
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
--
Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
On Thu, May 26, 2022 at 12:42:30PM -0400, Craig Rodrigues wrote:
Hi,
For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx.
I've started using these Actions:
https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action
docs: https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima...
These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers.
Are there equivalent GitHub Actions for using podman?
Its focus is broader, so it includes actions focused on integrating with OpenShift, but the "redhat-actions" organization includes a few actions I've been meaning to try out to get familiar with actions in general, and automating some builds/pushes that I currently do by running a script: https://github.com/redhat-actions/podman-login https://github.com/redhat-actions/buildah-build https://github.com/redhat-actions/push-to-registry The names, at least, suggest that they aim to fill similar roles. HTH, Nalin
Craig, I think you are confusing my confusion ;-) My point is, we're not going to invest in #2 on Ubuntu. Sure, we could. Not gonna do it, unless it puts RHEL where I want it to be. Why on Earth would we spend engineering resources to enable Ubuntu runners on GitHub Actions? And, yes right after I fired off the email, I realized these were implemented by Docker, not GitHub (the company). I view this as a two part Feature: 1. Make RHEL available as a runner at GitHub. This would justify investment in building #2 2. Create GitHub actions code for automation, which would live in the containers (aka Podman) community 3. Perhaps productize these as some sort of RHEL/UBI content which people could depend on Red Hat for. AKA, a productized version of #2. But, getting #1 done first is key, because our goals as a company are not to use Podman engineers to enable Ubuntu in a key place where developer eyeballs and fingers are working. This is essentially free marketing which we should not leave on the table. Also, this ties into a much bigger, strategic initiative that I have as the RHEL Server product manager - make RHEL available everywhere (GitHub Actions, make it work in GitLab (still working on that), make UBI an Official Image on DockerHub, build out Podman Desktop for Mac/Windows, enable RHEL in WSL2. There's a common theme to all of these. Availability of RHEL. In marketing there's the concept of zero, first, second, and third moments of truth. I won't bore you with all of the details, but we're failing (worst) at the first moment of truth. The customer goes into the frozen pizza aisle and there's no Red Baron pizza to even buy. In this case, it's no RHEL available at GitHub Actions (as well as Digital Ocean, Linode, CircleCI, CirrusCI, Windows Store for WSL2, etc). We need the Red Baron pizza in the frozen foods section at all grocery stores. Then, it's worth building out automation to drive consumption. Best Regards Scott M On Thu, May 26, 2022 at 3:52 PM Nalin Dahyabhai <nalin@redhat.com> wrote:
On Thu, May 26, 2022 at 12:42:30PM -0400, Craig Rodrigues wrote:
Hi,
For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx.
I've started using these Actions:
https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action
docs:
https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima...
These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers.
Are there equivalent GitHub Actions for using podman?
Its focus is broader, so it includes actions focused on integrating with OpenShift, but the "redhat-actions" organization includes a few actions I've been meaning to try out to get familiar with actions in general, and automating some builds/pushes that I currently do by running a script:
https://github.com/redhat-actions/podman-login https://github.com/redhat-actions/buildah-build https://github.com/redhat-actions/push-to-registry
The names, at least, suggest that they aim to fill similar roles.
HTH,
Nalin _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
-- <https://www.redhat.com/en/about/press-releases/red-hat-defines-new-epicenter-innovation-red-hat-enterprise-linux-9> Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
Also, I get that people could use custom RHEL runners which they deploy themselves, but I also don't think that's a great win, but maybe? I'd be willing to be convinced :-) But, I still think #1 is make RHEL available as a runner. On Thu, May 26, 2022 at 4:56 PM Scott McCarty <smccarty@redhat.com> wrote:
Craig, I think you are confusing my confusion ;-)
My point is, we're not going to invest in #2 on Ubuntu. Sure, we could. Not gonna do it, unless it puts RHEL where I want it to be. Why on Earth would we spend engineering resources to enable Ubuntu runners on GitHub Actions?
And, yes right after I fired off the email, I realized these were implemented by Docker, not GitHub (the company). I view this as a two part Feature:
1. Make RHEL available as a runner at GitHub. This would justify investment in building #2 2. Create GitHub actions code for automation, which would live in the containers (aka Podman) community 3. Perhaps productize these as some sort of RHEL/UBI content which people could depend on Red Hat for. AKA, a productized version of #2.
But, getting #1 done first is key, because our goals as a company are not to use Podman engineers to enable Ubuntu in a key place where developer eyeballs and fingers are working. This is essentially free marketing which we should not leave on the table. Also, this ties into a much bigger, strategic initiative that I have as the RHEL Server product manager - make RHEL available everywhere (GitHub Actions, make it work in GitLab (still working on that), make UBI an Official Image on DockerHub, build out Podman Desktop for Mac/Windows, enable RHEL in WSL2. There's a common theme to all of these. Availability of RHEL.
In marketing there's the concept of zero, first, second, and third moments of truth. I won't bore you with all of the details, but we're failing (worst) at the first moment of truth. The customer goes into the frozen pizza aisle and there's no Red Baron pizza to even buy. In this case, it's no RHEL available at GitHub Actions (as well as Digital Ocean, Linode, CircleCI, CirrusCI, Windows Store for WSL2, etc). We need the Red Baron pizza in the frozen foods section at all grocery stores.
Then, it's worth building out automation to drive consumption.
Best Regards Scott M
On Thu, May 26, 2022 at 3:52 PM Nalin Dahyabhai <nalin@redhat.com> wrote:
On Thu, May 26, 2022 at 12:42:30PM -0400, Craig Rodrigues wrote:
Hi,
For Docker, there are a number of GitHub Actions with good documentation that can be used to build containers, and push them to registries using docker build/buildx.
I've started using these Actions:
https://github.com/docker/setup-buildx-action/ https://github.com/docker/docker-login-action/ https://github.com/docker/build-push-action https://github.com/docker/metadata-action
docs:
https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima...
These docs and actions are actually quite good when setting up automation in GitHub for building/pushing containers.
Are there equivalent GitHub Actions for using podman?
Its focus is broader, so it includes actions focused on integrating with OpenShift, but the "redhat-actions" organization includes a few actions I've been meaning to try out to get familiar with actions in general, and automating some builds/pushes that I currently do by running a script:
https://github.com/redhat-actions/podman-login https://github.com/redhat-actions/buildah-build https://github.com/redhat-actions/push-to-registry
The names, at least, suggest that they aim to fill similar roles.
HTH,
Nalin _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
--
Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
-- <https://www.redhat.com/en/about/press-releases/red-hat-defines-new-epicenter-innovation-red-hat-enterprise-linux-9> Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
On Thu, May 26, 2022 at 4:56 PM Scott McCarty <smccarty@redhat.com> wrote:
1. Make RHEL available as a runner at GitHub. This would justify
investment in building #2
2. Create GitHub actions code for automation, which would live in the containers (aka Podman) community 3. Perhaps productize these as some sort of RHEL/UBI content which people could depend on Red Hat for. AKA, a productized version of #2.
Scott, Nalin has pointed out these GitHub Actions: https://github.com/redhat-actions/podman-login https://github.com/redhat-actions/buildah-build https://github.com/redhat-actions/push-to-registry In the documentation for https://github.com/redhat-actions/podman-login, there is this: *This action only runs on Linux, as it uses podman to perform the log in.* *GitHub's Ubuntu action runners come with Podman preinstalled.* *If you are not using those runners, you must first install Podman.* So from reading this, my understanding is that: 1. GitHub Actions using podman and buildah do exist 2. These GitHub Actions run on existing Github Ubuntu action runners 3. These Actions are not dependent on RHEL Is my understanding correct? -- Craig
Craig, I wanted to clarify a few things because I was definitely responding too quickly yesterday, so my apologies! First, I had no idea those Red Hat repos for GitHub Actions existed already on GitHub. We're a big company with a lot of smart motivated people, with a lot of different opinions, so it can be difficult to track all of the work that "we" (the greater community as well as just internal Red Hat people) are doing. Since somebody already built those GitHub Actions (I'm not sure who), I see no reason not to use them. At some point, I'd love to get RHEL out as a runner and then convert them over, but I see no reason to "not use Ubuntu" as Podman is a community project and people seem like they may already be using them. Being super honest, I read your email too quickly yesterday and I thought you were a Red Hat person asking for Red Hat engineering and product management about this! It happens all the time, and you may have detected a bit of frustrationin my response, or at a minimum terseness. I apologize for that! The confusing thing for me is, I would have thought the Communtiy repos ( github.com/containers) would provide GitHub Actions code for Ubuntu runners, while one might expect the Red Hat repos to have ones for RHEL runners. Or in a perfect world, the community ones would support both an Ubuntu runner and a RHEL runner (if I can get one created). Either way, it's definitely confusing. I'll try to hunt down whoever created the Red Hat ones and talk about moving them into the community. I think you are right, this is where I would expect to find them as well. Let me redefine my what I'd like to see in a perfect world: 1. Get rid of repos in Red Hat repo (but, I don't want to remove them if that would break people) 2. Have upstream GitHub Actions in the /containers repos (support Ubuntu runners today, maybe support both RHEL as well someday) 3. Have a downstream, productized Actions code which uses RHEL exclusively (maybe supports custom UBI runners, RHEL VM runners, and a potential RHEL instance on GitHub in the future). This might live back in the Red Hat repo or somewhere else, I'm not sure. Well, sorry for the weird interaction and confusion. I hope this helps. Best Regards Scott M On Thu, May 26, 2022, 5:13 PM Craig Rodrigues <rodrigc@crodrigues.org> wrote:
On Thu, May 26, 2022 at 4:56 PM Scott McCarty <smccarty@redhat.com> wrote:
1. Make RHEL available as a runner at GitHub. This would justify
2. Create GitHub actions code for automation, which would live in the containers (aka Podman) community 3. Perhaps productize these as some sort of RHEL/UBI content which
investment in building #2 people could depend on Red Hat for. AKA, a productized version of #2.
Scott,
Nalin has pointed out these GitHub Actions:
https://github.com/redhat-actions/podman-login https://github.com/redhat-actions/buildah-build https://github.com/redhat-actions/push-to-registry
In the documentation for https://github.com/redhat-actions/podman-login, there is this:
*This action only runs on Linux, as it uses podman to perform the log in.* *GitHub's Ubuntu action runners come with Podman preinstalled.* *If you are not using those runners, you must first install Podman.*
So from reading this, my understanding is that:
1. GitHub Actions using podman and buildah do exist 2. These GitHub Actions run on existing Github Ubuntu action runners 3. These Actions are not dependent on RHEL
Is my understanding correct? -- Craig _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Scott, My understanding is that GitHub offers "GitHub-hosted" where GitHub (the company) provides the hardware and software for runners on these platforms: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-... These platforms are Ubuntu, macOS, Windows. RHEL is not in that list. However, GitHub also offers "self-hosted" runners, where the user provides the hardware for the runner. The supported platforms for "self-hosted" runners are: https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hoste... RHEL and Centos *are* in that list. In terms of the GitHub Actions, for running podman, my opinion is that it would be ideal if these Actions could: 1. Work well on "GitHub-hosted" or "self-hosted" runners on Ubuntu, RHEL, or Centos 2. Be well documented, with docs that show up quickly via web search, and are as good as the docs from GitHub/Docker: https://docs.github.com/en/actions/publishing-packages/publishing-docker-ima... A few of the "stretch" goals that you mentioned: 1. Actions should move from https://github.com/redhat-actions to https://github.com/containers and be maintained by the community. I see value in that, since it would be nice to have an active community-maintained Actions. However, if these actions remain where they are and don't move for a while, that's probably OK. 2. "GitHub-hosted" runners should offer RHEL alongside Ubuntu. That would probably involve a longer discussion between GitHub and Red Hat. I see value in this, but this is not important to me since I am not using RHEL at the moment. However, since RHEL *is* supported for "self-hosted" runners, the priority to move forward on this might be -- Craig On Fri, May 27, 2022 at 5:53 AM Scott McCarty <smccarty@redhat.com> wrote:
1. Get rid of repos in Red Hat repo (but, I don't want to remove them if that would break people) 2. Have upstream GitHub Actions in the /containers repos (support Ubuntu runners today, maybe support both RHEL as well someday) 3. Have a downstream, productized Actions code which uses RHEL exclusively (maybe supports custom UBI runners, RHEL VM runners, and a potential RHEL instance on GitHub in the future). This might live back in the Red Hat repo or somewhere else, I'm not sure.
participants (4)
-
Craig Rodrigues -
Nalin Dahyabhai -
Scott McCarty -
v