containers / bootc

Boot and upgrade via container images

Home Page:https://containers.github.io/bootc/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Hook into https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/

cgwalters opened this issue · comments

I think it'd make sense to have this project also shipped in the big https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/packages/ COPR repo for Fedora.

What's the pattern to follow for this? I see https://github.com/containers/netavark/blob/main/netavark.spec.rpkg - is that in use?

It appears as so https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/package/netavark/ it looks like it's activated from a GitHub webhook. If a spec isn't already written I'm happy to take a try.

There's also https://packit.dev/ too...

OK, I made significant progress on this after #36
and https://copr.fedorainfracloud.org/coprs/walters/bootc/ is now up.

So...let's basically move that to say https://copr.fedorainfracloud.org/coprs/rhcontainerbot/bootc ?

I think it'd make sense to have this project also shipped in the big https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/packages/ COPR repo for Fedora.

sure thing. You now have full access to that copr now.

What's the pattern to follow for this? I see https://github.com/containers/netavark/blob/main/netavark.spec.rpkg - is that in use?

Yes, a spec like that in the main bootc dir and a github webhook https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/integrations/

Podman, Buildah and Skopeo use similar specs.

OK, I made significant progress on this after #36 and https://copr.fedorainfracloud.org/coprs/walters/bootc/ is now up.

So...let's basically move that to say https://copr.fedorainfracloud.org/coprs/rhcontainerbot/bootc ?

I can set that up too if you prefer a separate one.

sure thing. You now have full access to that copr now.

Oops, I think I somehow thought I was requesting permissions for the rhcontainerbot/ namespace, not the podman-next.

I think we do actually want a separate bootc one.

It seems like rhcontainerbot is a user account and not a group? It'd seem to make sense to have a group instead, like we do with e.g. https://copr.fedorainfracloud.org/coprs/g/CoreOS/

But anyways, for now can you create a rhcontainerbot/bootc project and add me - or even just the existing CoreOS FAS group as admins?

This is done! Thanks everyone!