That was easy!

- podman pull ghcr.io/some-natalie/jekyll-in-a-can
- podman login myforge.mydomain.tld
- podman push ghcr.io/some-natalie/jekyll-in-a-can myforge.mydomain.tld/webhosting/jekyll-in-a-can:latest

and now I can use myforge.mydomain.tld/webhosting/jekyll-in-a-can:latest in my Forgejo Action script to use the locally stored container image :)

TL;DR Forgejo offers an integrated OCI compliant container registry to provide container images!

#forgejo #selfhost #container

(I did have to add `client_max_body_size 500M;` to the `server` entry for my forgejo in nginx, which is the reverse proxy for my forgejo container, so I can upload big blobs. Without that the push fails with an "entity too large" error) Documentation of the integrated container registry is at https://forgejo.org/docs/latest/user/packages/container/
Container Registry | Forgejo – Beyond coding. We forge.

You want to use #Forgejo to build RPMs *and* offer them to your RHEL/Fedora/CentOS/Rocky machines with dnf or yum? Forgejo got you covered :) https://forgejo.org/docs/latest/user/packages/rpm/
RPM Package Registry | Forgejo – Beyond coding. We forge.

You want different packages? The list of supported formats is quite extensive :) https://forgejo.org/docs/latest/user/packages/#supported-package-managers
Package Registry | Forgejo – Beyond coding. We forge.

@jwildeboer impressive! I wonder if they use some tools to automate the process with support for multiple packaging formats.